Systems and Methods for Presenting Security Questions via Connected Security System

ABSTRACT

The various implementations described herein include methods, devices and systems for detecting trigger events and executing security protocols. In one aspect, a method is performed at a server system that is coupled to a smart device system and a client device, the smart device system located at a premises. The server system: (1) detects an unverified user within the premises based on data collected by the smart device system, wherein the data is communicated to the server system via the wide area networks; (2) provides a notification regarding the unverified user to authorized users via the wide area networks; (3) receives, from a first authorized user, a first user input in response to the notification; and (4) in response to receiving the first user input, executes a security operation at the premises based on the first user input.

RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S.application Ser. No. 15/877,239, filed Jan. 22, 2018, entitled “Systemsand Methods for Presenting Security Questions via Connected SecuritySystem,” which is a continuation of U.S. application Ser. No.14/697,505, filed Apr. 27, 2015, now U.S. Pat. No. 9,875,647, issued onJan. 23, 2018, entitled “Systems and Methods for Presenting SecurityQuestions via Connected Security System,” each of which is herebyincorporated by reference in its entirety.

TECHNICAL FIELD

This relates generally to security systems, including but not limited tomethods and systems for detecting trigger events and executing securityprotocols.

BACKGROUND

Security systems have traditionally lacked granularity with respect toidentifying and classifying a detected threat. An armed system thatdetects movement on a premises, for example, will trigger an alarmregardless of whether the cause truly warrants an alarm. Consequently,isolating false alarm scenarios from legitimate threats within anenvironment has long been a challenge with typical security systems.

SUMMARY

Accordingly, there is a need for methods, systems, and interfaces fordetecting trigger events and executing security protocols. By utilizinginformation and data gathered by one or more devices or systems in aconnected network, precise and accurate context is provided with respectto events that trigger an alarm in an environment. Furthermore, byexecuting predefined security protocols in response, such as presentingunverified users with security questions that they must correctlyanswer, false alarm scenarios can be better distinguished fromlegitimate threats and proper actions can be taken in response.

In accordance with some implementations, a method is performed at acomputer system (e.g., one or more smart devices in a smart homenetwork) with one or more processors and memory storing instructions forexecution by the one or more processors. The method includes detecting atrigger event, including detecting an unverified user within thepremises. A notification is provided regarding the detected triggerevent to one or more authorized users distinct from the unverified user.The method further includes receiving, from a first authorized user ofthe one or more authorized users, a first user input responsive to thenotification and corresponding to instructions to execute a firstsecurity protocol. In response to receiving the first user input, thefirst security protocol is executed. Executing the first securityprotocol includes presenting to the unverified user an authenticationrequest and monitoring the premises for a response to the authenticationrequest. Furthermore, executing the first security protocol includesexecuting or declining to execute a second security protocol based onthe response to the authentication request.

In accordance with some implementations, a computer system (e.g., one ormore smart devices in a smart home network) includes one or moreprocessors, memory, and one or more programs; the one or more programsare stored in the memory and configured to be executed by the one ormore processors. The one or more programs include instructions forperforming the operations of the method described above. In accordancewith some implementations, a non-transitory computer-readable storagemedium has stored therein instructions that, when executed by thecomputer system, cause the computer system to perform the operations ofthe method described above.

Thus, computer systems are provided with more effective and efficientmethods for detecting trigger events and executing security protocols,thereby increasing the effectiveness and efficiency of such devices andsystems.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described implementations,reference should be made to the Description of Implementations below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1 is an example smart home environment, in accordance with someimplementations.

FIG. 2 is a block diagram illustrating an example network architecturethat includes a smart home network, in accordance with someimplementations.

FIG. 3 illustrates a network-level view of an extensible devices andservices platform with which the smart home environment of FIG. 1 isintegrated, in accordance with some implementations.

FIG. 4 illustrates an abstracted functional view of the extensibledevices and services platform of FIG. 3, with reference to a processingengine as well as devices of the smart home environment, in accordancewith some implementations.

FIG. 5 is a representative operating environment in which a hub deviceserver system interacts with client devices and hub devicescommunicatively coupled to local smart devices, in accordance with someimplementations.

FIG. 6 is a block diagram illustrating a representative hub device, inaccordance with some implementations.

FIG. 7 is a block diagram illustrating a representative hub serversystem, in accordance with some implementations.

FIG. 8 is a block diagram illustrating a representative client deviceassociated with a user account, in accordance with some implementations.

FIG. 9 is a block diagram illustrating a representative smart device, inaccordance with some implementations.

FIG. 10 is a block diagram illustrating a representative smart homeprovider server system, in accordance with some implementations.

FIG. 11 is an example smart security network, in accordance with someimplementations.

FIG. 12 is an example smart home environment in a smart securitynetwork, in accordance with some implementations.

FIGS. 13A-13D illustrate examples of graphical user interfaces fordisplaying notifications and executing operations responsive tonotifications, in accordance with some implementations.

FIGS. 14A-14E are flow diagrams illustrating a method of detectingtrigger events and executing security protocols, in accordance with someimplementations.

Like reference numerals refer to corresponding parts throughout theseveral views of the drawings.

DESCRIPTION OF IMPLEMENTATIONS

Reference will now be made in detail to implementations, examples ofwhich are illustrated in the accompanying drawings. In the followingdetailed description, numerous specific details are set forth in orderto provide a thorough understanding of the various describedimplementations. However, it will be apparent to one of ordinary skillin the art that the various described implementations may be practicedwithout these specific details. In other instances, well-known methods,procedures, components, circuits, and networks have not been describedin detail so as not to unnecessarily obscure aspects of theimplementations.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first type ofsecurity protocol could be termed a second type of security protocol,and, similarly, a second type of security protocol could be termed afirst type of security protocol, without departing from the scope of thevarious described implementations. The first type of security protocoland the second type of security protocol are both types of securityprotocols, but they are not the same type of security protocol.

The terminology used in the description of the various describedimplementations herein is for the purpose of describing particularimplementations only and is not intended to be limiting. As used in thedescription of the various described implementations and the appendedclaims, the singular forms “a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting”or “in accordance with a determination that,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event]” or “in accordance with a determination that [astated condition or event] is detected,” depending on the context.

It is to be appreciated that “smart home environments” may refer tosmart environments for homes such as a single-family house, but thescope of the present teachings is not so limited. The present teachingsare also applicable, without limitation, to duplexes, townhomes,multi-unit apartment buildings, hotels, retail stores, office buildings,industrial buildings, and more generally any living space or work space.

It is also to be appreciated that while the terms user, customer,installer, homeowner, occupant, guest, tenant, landlord, repair person,and the like may be used to refer to the person or persons acting in thecontext of some particularly situations described herein, thesereferences do not limit the scope of the present teachings with respectto the person or persons who are performing such actions. Thus, forexample, the terms user, customer, purchaser, installer, subscriber, andhomeowner may often refer to the same person in the case of asingle-family residential dwelling, because the head of the household isoften the person who makes the purchasing decision, buys the unit, andinstalls and configures the unit, and is also one of the users of theunit. However, in other scenarios, such as a landlord-tenantenvironment, the customer may be the landlord with respect to purchasingthe unit, the installer may be a local apartment supervisor, a firstuser may be the tenant, and a second user may again be the landlord withrespect to remote control functionality. Importantly, while the identityof the person performing the action may be germane to a particularadvantage provided by one or more of the implementations, such identityshould not be construed in the descriptions that follow as necessarilylimiting the scope of the present teachings to those particularindividuals having those particular identities.

FIG. 1 is an example smart home environment 100 in accordance with someimplementations. The Smart home environment 100 includes a structure 150(e.g., a house, office building, garage, or mobile home) with variousintegrated devices. It will be appreciated that devices may also beintegrated into a smart home environment 100 that does not include anentire structure 150, such as an apartment, condominium, or officespace. Further, the smart home environment 100 may control and/or becoupled to devices outside of the actual structure 150. Indeed, severaldevices in the smart home environment 100 need not be physically withinthe structure 150. For example, a device controlling a pool heater 114or irrigation system 116 may be located outside of the structure 150.

The depicted structure 150 includes a plurality of rooms 152, separatedat least partly from each other via walls 154. The walls 154 may includeinterior walls or exterior walls. Each room may further include a floor156 and a ceiling 158. Devices may be mounted on, integrated with and/orsupported by a wall 154, floor 156 or ceiling 158.

In some implementations, the integrated devices of the smart homeenvironment 100 include intelligent, multi-sensing, network-connecteddevices that integrate seamlessly with each other in a smart homenetwork (e.g., 202 FIG. 2) and/or with a central server or acloud-computing system to provide a variety of useful smart homefunctions. The smart home environment 100 may include one or moreintelligent, multi-sensing, network-connected thermostats 102(hereinafter referred to as “smart thermostats 102”), one or moreintelligent, network-connected, multi-sensing hazard detection units 104(hereinafter referred to as “smart hazard detectors 104”), one or moreintelligent, multi-sensing, network-connected entryway interface devices106 and 120 (hereinafter referred to as “smart doorbells 106” and “smartdoorlocks 120”), and one or more intelligent, multi-sensing,network-connected alarm systems 122 (hereinafter referred to as “smartalarm systems 122”).

In some implementations, the one or more smart thermostats 102 detectambient climate characteristics (e.g., temperature and/or humidity) andcontrol a HVAC system 103 accordingly. For example, a respective smartthermostat 102 includes an ambient temperature sensor.

The one or more smart hazard detectors 104 may include thermal radiationsensors directed at respective heat sources (e.g., a stove, oven, otherappliances, a fireplace, etc.). For example, a smart hazard detector 104in a kitchen 153 includes a thermal radiation sensor directed at astove/oven 112. A thermal radiation sensor may determine the temperatureof the respective heat source (or a portion thereof) at which it isdirected and may provide corresponding blackbody radiation data asoutput.

The smart doorbell 106 and/or the smart doorlock 120 may detect aperson's approach to or departure from a location (e.g., an outer door),control doorbell/door locking functionality (e.g., receive user inputsfrom a portable electronic device 166-1 to actuate bolt of the smartdoorlock 120), announce a person's approach or departure via audio orvisual means, and/or control settings on a security system (e.g., toactivate or deactivate the security system when occupants go and come).

The smart alarm system 122 may detect the presence of an individualwithin close proximity (e.g., using built-in IR sensors), sound an alarm(e.g., through a built-in speaker, or by sending commands to one or moreexternal speakers), and send notifications to entities or userswithin/outside of the smart home network 100. In some implementations,the smart alarm system 122 also includes one or more input devices orsensors (e.g., keypad, biometric scanner, NFC transceiver, microphone)for verifying the identity of a user, and one or more output devices(e.g., display, speaker). In some implementations, the smart alarmsystem 122 may also be set to an “armed” mode, such that detection of atrigger condition or event causes the alarm to be sounded unless adisarming action is performed.

In some implementations, the smart home environment 100 includes one ormore intelligent, multi-sensing, network-connected wall switches 108(hereinafter referred to as “smart wall switches 108”), along with oneor more intelligent, multi-sensing, network-connected wall pluginterfaces 110 (hereinafter referred to as “smart wall plugs 110”). Thesmart wall switches 108 may detect ambient lighting conditions, detectroom-occupancy states, and control a power and/or dim state of one ormore lights. In some instances, smart wall switches 108 may also controla power state or speed of a fan, such as a ceiling fan. The smart wallplugs 110 may detect occupancy of a room or enclosure and control supplyof power to one or more wall plugs (e.g., such that power is notsupplied to the plug if nobody is at home).

In some implementations, the smart home environment 100 of FIG. 1includes a plurality of intelligent, multi-sensing, network-connectedappliances 112 (hereinafter referred to as “smart appliances 112”), suchas refrigerators, stoves, ovens, televisions, washers, dryers, lights,stereos, intercom systems, garage-door openers, floor fans, ceilingfans, wall air conditioners, pool heaters, irrigation systems, securitysystems, space heaters, window AC units, motorized duct vents, and soforth. In some implementations, when plugged in, an appliance mayannounce itself to the smart home network, such as by indicating whattype of appliance it is, and it may automatically integrate with thecontrols of the smart home. Such communication by the appliance to thesmart home may be facilitated by either a wired or wirelesscommunication protocol. The smart home may also include a variety ofnon-communicating legacy appliances 140, such as old conventionalwasher/dryers, refrigerators, and the like, which may be controlled bysmart wall plugs 110. The smart home environment 100 may further includea variety of partially communicating legacy appliances 142, such asinfrared (“IR”) controlled wall air conditioners or other IR-controlleddevices, which may be controlled by IR signals provided by the smarthazard detectors 104 or the smart wall switches 108.

In some implementations, the smart home environment 100 includes one ormore network-connected cameras 118 that are configured to provide videomonitoring and security in the smart home environment 100. The cameras118 may be used to determine occupancy of the structure 150 and/orparticular rooms 152 in the structure 150, and thus may act as occupancysensors. For example, video captured by the cameras 118 may be processedto identify the presence of an occupant in the structure 150 (e.g., in aparticular room 152). Specific individuals may be identified based, forexample, on their appearance (e.g., height, face) and/or movement (e.g.,their walk/gait). Cameras 118 may additionally include one or moresensors (e.g., IR sensors, motion detectors), input devices (e.g.,microphone for capturing audio), and output devices (e.g., speaker foroutputting audio).

The smart home environment 100 may additionally or alternatively includeone or more other occupancy sensors (e.g., the smart doorbell 106, smartdoorlocks 120, touch screens, IR sensors, microphones, ambient lightsensors, motion detectors, smart nightlights 170, etc.). In someimplementations, the smart home environment 100 includes radio-frequencyidentification (RFID) readers (e.g., in each room 152 or a portionthereof) that determine occupancy based on RFID tags located on orembedded in occupants. For example, RFID readers may be integrated intothe smart hazard detectors 104.

The smart home environment 100 may also include communication withdevices outside of the physical home but within a proximate geographicalrange of the home. For example, the smart home environment 100 mayinclude a pool heater monitor 114 that communicates a current pooltemperature to other devices within the smart home environment 100and/or receives commands for controlling the pool temperature.Similarly, the smart home environment 100 may include an irrigationmonitor 116 that communicates information regarding irrigation systemswithin the smart home environment 100 and/or receives controlinformation for controlling such irrigation systems.

By virtue of network connectivity, one or more of the smart home devicesof FIG. 1 may further allow a user to interact with the device even ifthe user is not proximate to the device. For example, a user maycommunicate with a device using a computer (e.g., a desktop computer,laptop computer, or tablet) or other portable electronic device 166(e.g., a mobile phone, such as a smart phone). A webpage or applicationmay be configured to receive communications from the user and controlthe device based on the communications and/or to present informationabout the device's operation to the user. For example, the user may viewa current set point temperature for a device (e.g., a stove) and adjustit using a computer. The user may be in the structure during this remotecommunication or outside the structure.

As discussed above, users may control smart devices in the smart homeenvironment 100 using a network-connected computer or portableelectronic device 166. In some examples, some or all of the occupants(e.g., individuals who live in the home) may register their device 166with the smart home environment 100. Such registration may be made at acentral server to authenticate the occupant and/or the device as beingassociated with the home and to give permission to the occupant to usethe device to control the smart devices in the home. An occupant may usetheir registered device 166 to remotely control the smart devices of thehome, such as when the occupant is at work or on vacation. The occupantmay also use their registered device to control the smart devices whenthe occupant is actually located inside the home, such as when theoccupant is sitting on a couch inside the home. It should be appreciatedthat instead of or in addition to registering devices 166, the smarthome environment 100 may make inferences about which individuals live inthe home and are therefore occupants and which devices 166 areassociated with those individuals. As such, the smart home environmentmay “learn” who is an occupant and permit the devices 166 associatedwith those individuals to control the smart devices of the home.

In some implementations, in addition to containing processing andsensing capabilities, devices 102, 104, 106, 108, 110, 112, 114, 116,118, 120, and/or 122 (collectively referred to as “the smart devices”)are capable of data communications and information sharing with othersmart devices, a central server or cloud-computing system, and/or otherdevices that are network-connected. Data communications may be carriedout using any of a variety of custom or standard wireless protocols(e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, BluetoothSmart, ISA100.11a, WirelessHART, MiWi, etc.) and/or any of a variety ofcustom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), orany other suitable communication protocol, including communicationprotocols not yet developed as of the filing date of this document.

In some implementations, the smart devices serve as wireless or wiredrepeaters. In some implementations, a first one of the smart devicescommunicates with a second one of the smart devices via a wirelessrouter. The smart devices may further communicate with each other via aconnection (e.g., network interface 160) to a network, such as theInternet 162. Through the Internet 162, the smart devices maycommunicate with a smart home provider server system 164 (also called acentral server system and/or a cloud-computing system herein). The smarthome provider server system 164 may be associated with a manufacturer,support entity, or service provider associated with the smart device(s).In some implementations, a user is able to contact customer supportusing a smart device itself rather than needing to use othercommunication means, such as a telephone or Internet-connected computer.In some implementations, software updates are automatically sent fromthe smart home provider server system 164 to smart devices (e.g., whenavailable, when purchased, or at routine intervals).

In some implementations, the network interface 160 includes aconventional network device (e.g., a router), and the smart homeenvironment 100 of FIG. 1 includes a hub device 180 that iscommunicatively coupled to the network(s) 162 directly or via thenetwork interface 160. The hub device 180 is further communicativelycoupled to one or more of the above intelligent, multi-sensing,network-connected devices (e.g., smart devices of the smart homeenvironment 100). Each of these smart devices optionally communicateswith the hub device 180 using one or more radio communication networksavailable at least in the smart home environment 100 (e.g., ZigBee,Z-Wave, Insteon, Bluetooth, Wi-Fi and other radio communicationnetworks). In some implementations, the hub device 180 and devicescoupled with/to the hub device can be controlled and/or interacted withvia an application running on a smart phone, household controller,laptop, tablet computer, game console or similar electronic device. Insome implementations, a user of such controller application can viewstatus of the hub device or coupled smart devices, configure the hubdevice to interoperate with smart devices newly introduced to the homenetwork, commission new smart devices, and adjust or view settings ofconnected smart devices, etc. In some implementations the hub deviceextends capabilities of low capability smart device to matchcapabilities of the highly capable smart devices of the same type,integrates functionality of multiple different device types—even acrossdifferent communication protocols, and is configured to streamlineadding of new devices and commissioning of the hub device.

FIG. 2 is a block diagram illustrating an example network architecture200 that includes a smart home network 202 in accordance with someimplementations. In some implementations, the smart devices 204 in thesmart home environment 100 (e.g., devices 102, 104, 106, 108, 110, 112,114, 116, 118, 120, and/or 122) combine with the hub device 180 tocreate a mesh network in smart home network 202. In someimplementations, one or more smart devices 204 in the smart home network202 operate as a smart home controller. Additionally and/oralternatively, hub device 180 operates as the smart home controller. Insome implementations, a smart home controller has more computing powerthan other smart devices. In some implementations, a smart homecontroller processes inputs (e.g., from smart devices 204, electronicdevice 166, and/or smart home provider server system 164) and sendscommands (e.g., to smart devices 204 in the smart home network 202) tocontrol operation of the smart home environment 100. In someimplementations, some of the smart devices 204 in the smart home network202 (e.g., in the mesh network) are “spokesman” nodes (e.g., 204-1) andothers are “low-powered” nodes (e.g., 204-9). Some of the smart devicesin the smart home environment 100 are battery powered, while others havea regular and reliable power source, such as by connecting to wiring(e.g., to 120V line voltage wires) behind the walls 154 of the smarthome environment. The smart devices that have a regular and reliablepower source are referred to as “spokesman” nodes. These nodes aretypically equipped with the capability of using a wireless protocol tofacilitate bidirectional communication with a variety of other devicesin the smart home environment 100, as well as with the smart homeprovider server system 164. In some implementations, one or more“spokesman” nodes operate as a smart home controller. On the other hand,the devices that are battery powered are the “low-power” nodes. Thesenodes tend to be smaller than spokesman nodes and typically onlycommunicate using wireless protocols that require very little power,such as Zigbee, 6LoWPAN, etc.

In some implementations, some low-power nodes are incapable ofbidirectional communication. These low-power nodes send messages, butthey are unable to “listen”. Thus, other devices in the smart homeenvironment 100, such as the spokesman nodes, cannot send information tothese low-power nodes.

In some implementations, some low-power nodes are capable of only alimited bidirectional communication. For example, other devices are ableto communicate with the low-power nodes only during a certain timeperiod.

As described, in some implementations, the smart devices serve aslow-power and spokesman nodes to create a mesh network in the smart homeenvironment 100. In some implementations, individual low-power nodes inthe smart home environment regularly send out messages regarding whatthey are sensing, and the other low-powered nodes in the smart homeenvironment—in addition to sending out their own messages—forward themessages, thereby causing the messages to travel from node to node(i.e., device to device) throughout the smart home network 202. In someimplementations, the spokesman nodes in the smart home network 202,which are able to communicate using a relatively high-powercommunication protocol, such as IEEE 802.11, are able to switch to arelatively low-power communication protocol, such as IEEE 802.15.4, toreceive these messages, translate the messages to other communicationprotocols, and send the translated messages to other spokesman nodesand/or the smart home provider server system 164 (using, e.g., therelatively high-power communication protocol). Thus, the low-powerednodes using low-power communication protocols are able to send and/orreceive messages across the entire smart home network 202, as well asover the Internet 162 to the smart home provider server system 164. Insome implementations, the mesh network enables the smart home providerserver system 164 to regularly receive data from most or all of thesmart devices in the home, make inferences based on the data, facilitatestate synchronization across devices within and outside of the smarthome network 202, and send commands to one or more of the smart devicesto perform tasks in the smart home environment.

As described, the spokesman nodes and some of the low-powered nodes arecapable of “listening.” Accordingly, users, other devices, and/or thesmart home provider server system 164 may communicate control commandsto the low-powered nodes. For example, a user may use the electronicdevice 166 (e.g., a smart phone) to send commands over the Internet tothe smart home provider server system 164, which then relays thecommands to one or more spokesman nodes in the smart home network 202.The spokesman nodes may use a low-power protocol to communicate thecommands to the low-power nodes throughout the smart home network 202,as well as to other spokesman nodes that did not receive the commandsdirectly from the smart home provider server system 164.

In some implementations, a smart nightlight 170 (FIG. 1), which is anexample of a smart device 204, is a low-power node. In addition tohousing a light source, the smart nightlight 170 houses an occupancysensor, such as an ultrasonic or passive IR sensor, and an ambient lightsensor, such as a photo resistor or a single-pixel sensor that measureslight in the room. In some implementations, the smart nightlight 170 isconfigured to activate the light source when its ambient light sensordetects that the room is dark and when its occupancy sensor detects thatsomeone is in the room. In other implementations, the smart nightlight170 is simply configured to activate the light source when its ambientlight sensor detects that the room is dark. Further, in someimplementations, the smart nightlight 170 includes a low-power wirelesscommunication chip (e.g., a ZigBee chip) that regularly sends outmessages regarding the occupancy of the room and the amount of light inthe room, including instantaneous messages coincident with the occupancysensor detecting the presence of a person in the room. As mentionedabove, these messages may be sent wirelessly (e.g., using the meshnetwork) from node to node (i.e., smart device to smart device) withinthe smart home network 202 as well as over the Internet 162 to the smarthome provider server system 164.

Other examples of low-power nodes include battery-operated versions ofthe smart hazard detectors 104. These smart hazard detectors 104 areoften located in an area without access to constant and reliable powerand may include any number and type of sensors, such as smoke/fire/heatsensors (e.g., thermal radiation sensors), carbon monoxide/dioxidesensors, occupancy/motion sensors, ambient light sensors, ambienttemperature sensors, humidity sensors, and the like. Furthermore, smarthazard detectors 104 may send messages that correspond to each of therespective sensors to the other devices and/or the smart home providerserver system 164, such as by using the mesh network as described above.

Examples of spokesman nodes include smart doorbells 106, smartthermostats 102, smart wall switches 108, and smart wall plugs 110.These devices are often located near and connected to a reliable powersource, and therefore may include more power-consuming components, suchas one or more communication chips capable of bidirectionalcommunication in a variety of protocols.

In some implementations, the smart home environment 100 includes servicerobots 168 (FIG. 1) that are configured to carry out, in an autonomousmanner, any of a variety of household tasks.

As explained above with reference to FIG. 1, in some implementations,the smart home environment 100 of FIG. 1 includes a hub device 180 thatis communicatively coupled to the network(s) 162 directly or via thenetwork interface 160. The hub device 180 is further communicativelycoupled to one or more of the smart devices using a radio communicationnetwork that is available at least in the smart home environment 100.Communication protocols used by the radio communication network include,but are not limited to, ZigBee, Z-Wave, Insteon, EuOcean, Thread, OSIAN,Bluetooth Low Energy and the like. In some implementations, the hubdevice 180 not only converts the data received from each smart device tomeet the data format requirements of the network interface 160 or thenetwork(s) 162, but also converts information received from the networkinterface 160 or the network(s) 162 to meet the data format requirementsof the respective communication protocol associated with a targetedsmart device. In some implementations, in addition to data formatconversion, the hub device 180 further processes the data received fromthe smart devices or information received from the network interface 160or the network(s) 162 preliminary. For example, the hub device 180 canintegrate inputs from multiple sensors/connected devices (includingsensors/devices of the same and/or different types), perform higherlevel processing on those inputs—e.g., to assess the overall environmentand coordinate operation among the different sensors/devices—and/orprovide instructions to the different devices based on the collection ofinputs and programmed processing. It is also noted that in someimplementations, the network interface 160 and the hub device 180 areintegrated to one network device. Functionality described herein isrepresentative of particular implementations of smart devices, controlapplication(s) running on representative electronic device(s) (such as asmart phone), hub device(s) 180, and server(s) coupled to hub device(s)via the Internet or other Wide Area Network. All or a portion of thisfunctionality and associated operations can be performed by any elementsof the described system—for example, all or a portion of thefunctionality described herein as being performed by an implementationof the hub device can be performed, in different system implementations,in whole or in part on the server, one or more connected smart devicesand/or the control application, or different combinations thereof.

FIG. 3 illustrates a network-level view of an extensible devices andservices platform with which the smart home environment of FIG. 1 isintegrated, in accordance with some implementations. The extensibledevices and services platform 300 includes smart home provider serversystem 164. Each of the intelligent, network-connected devices describedwith reference to FIG. 1 (e.g., 102, 104, 106, 108, 110, 112, 114, 116and 118, identified simply as “devices” in FIGS. 2-4) may communicatewith the smart home provider server system 164. For example, aconnection to the Internet 162 may be established either directly (forexample, using 3G/4G connectivity to a wireless carrier), or through anetwork interface 160 (e.g., a router, switch, gateway, hub device, oran intelligent, dedicated whole-home controller node), or through anycombination thereof.

In some implementations, the devices and services platform 300communicates with and collects data from the smart devices of the smarthome environment 100. In addition, in some implementations, the devicesand services platform 300 communicates with and collects data from aplurality of smart home environments across the world. For example, thesmart home provider server system 164 collects home data 302 from thedevices of one or more smart home environments 100, where the devicesmay routinely transmit home data or may transmit home data in specificinstances (e.g., when a device queries the home data 302). Examplecollected home data 302 includes, without limitation, power consumptiondata, blackbody radiation data, occupancy data, HVAC settings and usagedata, carbon monoxide levels data, carbon dioxide levels data, volatileorganic compounds levels data, sleeping schedule data, cooking scheduledata, inside and outside temperature humidity data, televisionviewership data, inside and outside noise level data, pressure data,video data, etc.

In some implementations, the smart home provider server system 164provides one or more services 304 to smart homes and/or third parties.Example services 304 include, without limitation, software updates,customer support, sensor data collection/logging, remote access, remoteor distributed control, and/or use suggestions (e.g., based on collectedhome data 302) to improve performance, reduce utility cost, increasesafety, etc. In some implementations, data associated with the services304 is stored at the smart home provider server system 164, and thesmart home provider server system 164 retrieves and transmits the dataat appropriate times (e.g., at regular intervals, upon receiving arequest from a user, etc.).

In some implementations, the extensible devices and services platform300 includes a processing engine 306, which may be concentrated at asingle server or distributed among several different computing entitieswithout limitation. In some implementations, the processing engine 306includes engines configured to receive data from the devices of smarthome environments 100 (e.g., via the Internet 162 and/or a networkinterface 160), to index the data, to analyze the data and/or togenerate statistics based on the analysis or as part of the analysis. Insome implementations, the analyzed data is stored as derived home data308.

Results of the analysis or statistics may thereafter be transmitted backto the device that provided home data used to derive the results, toother devices, to a server providing a webpage to a user of the device,or to other non-smart device entities. In some implementations, usagestatistics, usage statistics relative to use of other devices, usagepatterns, and/or statistics summarizing sensor readings are generated bythe processing engine 306 and transmitted. The results or statistics maybe provided via the Internet 162. In this manner, the processing engine306 may be configured and programmed to derive a variety of usefulinformation from the home data 302. A single server may include one ormore processing engines.

The derived home data 308 may be used at different granularities for avariety of useful purposes, ranging from explicit programmed control ofthe devices on a per-home, per-neighborhood, or per-region basis (forexample, demand-response programs for electrical utilities), to thegeneration of inferential abstractions that may assist on a per-homebasis (for example, an inference may be drawn that the homeowner hasleft for vacation and so security detection equipment may be put onheightened sensitivity), to the generation of statistics and associatedinferential abstractions that may be used for government or charitablepurposes. For example, processing engine 306 may generate statisticsabout device usage across a population of devices and send thestatistics to device users, service providers or other entities (e.g.,entities that have requested the statistics and/or entities that haveprovided monetary compensation for the statistics).

In some implementations, to encourage innovation and research and toincrease products and services available to users, the devices andservices platform 300 exposes a range of application programminginterfaces (APIs) 310 to third parties, such as charities 314,governmental entities 316 (e.g., the Food and Drug Administration or theEnvironmental Protection Agency), academic institutions 318 (e.g.,university researchers), businesses 320 (e.g., providing devicewarranties or service to related equipment, targeting advertisementsbased on home data), utility companies 324, and other third parties. TheAPIs 310 are coupled to and permit third-party systems to communicatewith the smart home provider server system 164, including the services304, the processing engine 306, the home data 302, and the derived homedata 308. In some implementations, the APIs 310 allow applicationsexecuted by the third parties to initiate specific data processing tasksthat are executed by the smart home provider server system 164, as wellas to receive dynamic updates to the home data 302 and the derived homedata 308.

For example, third parties may develop programs and/or applications(e.g., web applications or mobile applications) that integrate with thesmart home provider server system 164 to provide services andinformation to users. Such programs and applications may be, forexample, designed to help users reduce energy consumption, topreemptively service faulty equipment, to prepare for high servicedemands, to track past service performance, etc., and/or to performother beneficial functions or tasks.

FIG. 4 illustrates an abstracted functional view 400 of the extensibledevices and services platform 300 of FIG. 3, with reference to aprocessing engine 306 as well as devices of the smart home environment,in accordance with some implementations. Even though devices situated insmart home environments will have a wide variety of different individualcapabilities and limitations, the devices may be thought of as sharingcommon characteristics in that each device is a data consumer 402 (DC),a data source 404 (DS), a services consumer 406 (SC), and a servicessource 408 (SS). Advantageously, in addition to providing controlinformation used by the devices to achieve their local and immediateobjectives, the extensible devices and services platform 300 may also beconfigured to use the large amount of data that is generated by thesedevices. In addition to enhancing or optimizing the actual operation ofthe devices themselves with respect to their immediate functions, theextensible devices and services platform 300 may be directed to“repurpose” that data in a variety of automated, extensible, flexible,and/or scalable ways to achieve a variety of useful objectives. Theseobjectives may be predefined or adaptively identified based on, e.g.,usage patterns, device efficiency, and/or user input (e.g., requestingspecific functionality).

FIG. 4 shows processing engine 306 as including a number of processingparadigms 410. In some implementations, processing engine 306 includes amanaged services paradigm 410 a that monitors and manages primary orsecondary device functions. The device functions may include ensuringproper operation of a device given user inputs, estimating that (e.g.,and responding to an instance in which) an intruder is or is attemptingto be in a dwelling, detecting a failure of equipment coupled to thedevice (e.g., a light bulb having burned out), implementing or otherwiseresponding to energy demand response events, providing a heat-sourcealert, and/or alerting a user of a current or predicted future event orcharacteristic. In some implementations, processing engine 306 includesan advertising/communication paradigm 410 b that estimatescharacteristics (e.g., demographic information), desires and/or productsof interest of a user based on device usage. Services, promotions,products or upgrades may then be offered or automatically provided tothe user. In some implementations, processing engine 306 includes asocial paradigm 410c that uses information from a social network,provides information to a social network (for example, based on deviceusage), and/or processes data associated with user and/or deviceinteractions with the social network platform. For example, a user'sstatus as reported to their trusted contacts on the social network maybe updated to indicate when the user is home based on light detection,security system inactivation or device usage detectors. As anotherexample, a user may be able to share device-usage statistics with otherusers. In yet another example, a user may share HVAC settings thatresult in low power bills and other users may download the HVAC settingsto their smart thermostat 102 to reduce their power bills.

In some implementations, processing engine 306 includes achallenges/rules/compliance/rewards paradigm 410d that informs a user ofchallenges, competitions, rules, compliance regulations and/or rewardsand/or that uses operation data to determine whether a challenge hasbeen met, a rule or regulation has been complied with and/or a rewardhas been earned. The challenges, rules, and/or regulations may relate toefforts to conserve energy, to live safely (e.g., reducing theoccurrence of heat-source alerts) (e.g., reducing exposure to toxins orcarcinogens), to conserve money and/or equipment life, to improvehealth, etc. For example, one challenge may involve participants turningdown their thermostat by one degree for one week. Those participantsthat successfully complete the challenge are rewarded, such as withcoupons, virtual currency, status, etc. Regarding compliance, an exampleinvolves a rental-property owner making a rule that no renters arepermitted to access certain owner's rooms. The devices in the roomhaving occupancy sensors may send updates to the owner when the room isaccessed.

In some implementations, processing engine 306 integrates or otherwiseuses extrinsic information 412 from extrinsic sources to improve thefunctioning of one or more processing paradigms. Extrinsic information412 may be used to interpret data received from a device, to determine acharacteristic of the environment near the device (e.g., outside astructure that the device is enclosed in), to determine services orproducts available to the user, to identify a social network orsocial-network information, to determine contact information of entities(e.g., public-service entities such as an emergency-response team, thepolice or a hospital) near the device, to identify statistical orenvironmental conditions, trends or other information associated with ahome or neighborhood, and so forth.

FIG. 5 illustrates a representative operating environment 500 in which ahub device server system 508 provides data processing for monitoring andfacilitating review of motion events in video streams captured by videocameras 118. As shown in FIG. 5, the hub device server system 508receives video data from video sources 522 (including cameras 118)located at various physical locations (e.g., inside homes, restaurants,stores, streets, parking lots, and/or the smart home environments 100 ofFIG. 1). Each video source 522 may be bound to one or more revieweraccounts, and the hub device server system 508 provides video monitoringdata for the video source 522 to client devices 504 associated with thereviewer accounts. For example, the portable electronic device 166 is anexample of the client device 504.

In some implementations, the smart home provider server system 164 or acomponent thereof serves as the hub device server system 508. In someimplementations, the hub device server system 508 is a dedicated videoprocessing server that provides video processing services to videosources and client devices 504 independent of other services provided bythe hub device server system 508.

In some implementations, each of the video sources 522 includes one ormore video cameras 118 that capture video and send the captured video tothe hub device server system 508 substantially in real-time. In someimplementations, each of the video sources 522 optionally includes acontroller device (not shown) that serves as an intermediary between theone or more cameras 118 and the hub device server system 508. Thecontroller device receives the video data from the one or more cameras118, optionally, performs some preliminary processing on the video data,and sends the video data to the hub device server system 508 on behalfof the one or more cameras 118 substantially in real-time. In someimplementations, each camera has its own on-board processingcapabilities to perform some preliminary processing on the capturedvideo data before sending the processed video data (along with metadataobtained through the preliminary processing) to the controller deviceand/or the hub device server system 508.

As shown in FIG. 5, in accordance with some implementations, each of theclient devices 504 includes a client-side module 502. The client-sidemodule 502 communicates with a server-side module 506 executed on thehub device server system 508 through the one or more networks 162. Theclient-side module 502 provides client-side functionalities for theevent monitoring and review processing and communications with theserver-side module 506. The server-side module 506 provides server-sidefunctionalities for event monitoring and review processing for anynumber of client-side modules 502 each residing on a respective clientdevice 504. The server-side module 506 also provides server-sidefunctionalities for video processing and camera control for any numberof the video sources 522, including any number of control devices andthe cameras 118.

In some implementations, the server-side module 506 includes one or moreprocessors 512, a video storage database 514, device and accountdatabases 516, an I/O interface to one or more client devices 518, andan I/O interface to one or more video sources 520. The I/O interface toone or more clients 518 facilitates the client-facing input and outputprocessing for the server-side module 506. The databases 516 store aplurality of profiles for reviewer accounts registered with the videoprocessing server, where a respective user profile includes accountcredentials for a respective reviewer account, and one or more videosources linked to the respective reviewer account. The I/O interface toone or more video sources 520 facilitates communications with one ormore video sources 522 (e.g., groups of one or more cameras 118 andassociated controller devices). The video storage database 514 storesraw video data received from the video sources 522, as well as varioustypes of metadata, such as motion events, event categories, eventcategory models, event filters, and event masks, for use in dataprocessing for event monitoring and review for each reviewer account.

Examples of a representative client device 504 include, but are notlimited to, a handheld computer, a wearable computing device, a personaldigital assistant (PDA), a tablet computer, a laptop computer, a desktopcomputer, a cellular telephone, a smart phone, an enhanced generalpacket radio service (EGPRS) mobile phone, a media player, a navigationdevice, a game console, a television, a remote control, a point-of-sale(POS) terminal, vehicle-mounted computer, an ebook reader, or acombination of any two or more of these data processing devices or otherdata processing devices.

Examples of the one or more networks 162 include local area networks(LAN) and wide area networks (WAN) such as the Internet. The one or morenetworks 162 are, optionally, implemented using any known networkprotocol, including various wired or wireless protocols, such asEthernet, Universal Serial Bus (USB), FIREWIRE, Long Term Evolution(LTE), Global System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), code division multiple access (CDMA), time divisionmultiple access (TDMA), Bluetooth, Wi-Fi, voice over Internet Protocol(VoIP), Wi-MAX, or any other suitable communication protocol.

In some implementations, the hub device server system 508 is implementedon one or more standalone data processing apparatuses or a distributednetwork of computers. In some implementations, the hub device serversystem 508 also employs various virtual devices and/or services of thirdparty service providers (e.g., third-party cloud service providers) toprovide the underlying computing resources and/or infrastructureresources of the hub device server system 508. In some implementations,the hub device server system 508 includes, but is not limited to, ahandheld computer, a tablet computer, a laptop computer, a desktopcomputer, or a combination of any two or more of these data processingdevices or other data processing devices.

The server-client environment 500 shown in FIG. 1 includes both aclient-side portion (e.g., the client-side module 502) and a server-sideportion (e.g., the server-side module 506). The division offunctionalities between the client and server portions of operatingenvironment 500 can vary in different implementations. Similarly, thedivision of functionalities between the video source 522 and the hubdevice server system 508 can vary in different implementations. Forexample, in some implementations, client-side module 502 is athin-client that provides only user-facing input and output processingfunctions, and delegates all other data processing functionalities to abackend server (e.g., the hub device server system 508). Similarly, insome implementations, a respective one of the video sources 522 is asimple video capturing device that continuously captures and streamsvideo data to the hub device server system 508 without no or limitedlocal preliminary processing on the video data. Although many aspects ofthe present technology are described from the perspective of the hubdevice server system 508, the corresponding actions performed by theclient device 504 and/or the video sources 522 would be apparent to onesskilled in the art without any creative efforts. Similarly, some aspectsof the present technology may be described from the perspective of theclient device or the video source, and the corresponding actionsperformed by the video server would be apparent to ones skilled in theart without any creative efforts. Furthermore, some aspects of thepresent technology may be performed by the hub device server system 508,the client device 504, and the video sources 522 cooperatively.

It should be understood that operating environment 500 that involves thehub device server system 508, the video sources 522 and the videocameras 118 is merely an example. Many aspects of operating environment500 are generally applicable in other operating environments in which aserver system provides data processing for monitoring and facilitatingreview of data captured by other types of electronic devices (e.g.,smart thermostats 102, smart hazard detectors 104, smart doorbells 106,smart wall plugs 110, appliances 112 and the like).

The electronic devices, the client devices or the server systemcommunicate with each other using the one or more communication networks162. In an example smart home environment, two or more devices (e.g.,the network interface device 160, the hub device 180, and the clientdevices 504-m) are located in close proximity to each other, such thatthey could be communicatively coupled in the same sub-network 162A viawired connections, a WLAN or a Bluetooth Personal Area Network (PAN).The Bluetooth PAN is optionally established based on classical Bluetoothtechnology or Bluetooth Low Energy (BLE) technology. This smart homeenvironment further includes one or more other radio communicationnetworks 162B through which at least some of the electronic devices ofthe video sources 522-n exchange data with the hub device 180.Alternatively, in some situations, some of the electronic devices of thevideo sources 522-n communicate with the network interface device 160directly via the same sub-network 162A that couples devices 160, 180 and504-m. In some implementations (e.g., in the network 162C), both theclient device 504-m and the electronic devices of the video sources522-n communicate directly via the network(s) 162 without passing thenetwork interface device 160 or the hub device 180.

In some implementations, during normal operation, the network interfacedevice 160 and the hub device 180 communicate with each other to form anetwork gateway through which data are exchanged with the electronicdevice of the video sources 522-n. As explained above, the networkinterface device 160 and the hub device 180 optionally communicate witheach other via a sub-network 162A.

FIG. 6 is a block diagram illustrating a representative hub device 180in accordance with some implementations. In some implementations, thehub device 180 includes one or more processing units (e.g., CPUs, ASICs,FPGAs, microprocessors, and the like) 602, one or more communicationinterfaces 604, memory 606, radios 640, and one or more communicationbuses 608 for interconnecting these components (sometimes called achipset). In some implementations, the hub device 180 includes one ormore input devices 610 such as one or more buttons for receiving input.In some implementations, the hub device 180 includes one or more outputdevices 612 such as one or more indicator lights, a sound card, aspeaker, a small display for displaying textual information and errorcodes, etc. Furthermore, in some implementations, the hub device 180uses a microphone and voice recognition or a camera and gesturerecognition to supplement or replace the keyboard. In someimplementations, the hub device 180 includes a location detection device614, such as a GPS (global positioning satellite) or other geo-locationreceiver, for determining the location of the hub device 180.

The hub device 180 optionally includes one or more built-in sensors (notshown), including, for example, one or more thermal radiation sensors,ambient temperature sensors, humidity sensors, IR sensors, occupancysensors (e.g., using RFID sensors), ambient light sensors, motiondetectors, accelerometers, and/or gyroscopes.

The radios 640 enables one or more radio communication networks in thesmart home environments, and allows a hub device to communicate withsmart devices. In some implementations, the radios 640 are capable ofdata communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) custom orstandard wired protocols (e.g., Ethernet, HomePlug, etc.), and/or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Communication interfaces 604 include, for example, hardware capable ofdata communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/orany of a variety of custom or standard wired protocols (e.g., Ethernet,HomePlug, etc.), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Memory 606 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 606, or alternatively the non-volatile memorywithin memory 606, includes a non-transitory computer readable storagemedium. In some implementations, memory 606, or the non-transitorycomputer readable storage medium of memory 606, stores the followingprograms, modules, and data structures, or a subset or superset thereof:

-   -   Operating logic 616 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Hub device communication module 618 for connecting to and        communicating with other network devices, systems, and entities        (e.g., network interface 160, such as a router that provides        Internet connectivity, networked storage devices, network        routing devices, server system 508, security call center 1102,        emergency responders 1104, smart home provider server system        164, client devices 504, smart home environments 100, etc.)        connected to one or more networks 162 via one or more        communication interfaces 604 (wired or wireless);    -   Radio Communication Module 620 for connecting the hub device 180        to other devices (e.g., controller devices, smart devices 204 in        smart home environment 100, client devices 504) via one or more        radio communication devices (e.g., radios 640);    -   User interface module 622 for providing and displaying a user        interface in which settings, captured data, and/or other data        for one or more devices (e.g., smart devices 204 in smart home        environment 100) can be configured and/or viewed, for displaying        notifications of trigger events (e.g., the GUI and notification        1300 of FIG. 13A), and/or for detecting user inputs (e.g., user        input indicating selection of a UI element, FIG. 13C);    -   Hub device database 624, including but not limited to:        -   Sensor information 6240 for storing and managing data            received, detected, and/or transmitted by one or more            sensors of the hub device 180 and/or one or more other            devices (e.g., smart devices 204 in smart home environment            100);        -   Device settings 6242 for storing operational settings for            one or more devices (e.g., coupled smart devices 204 in            smart home environment 100); and        -   Communication protocol information 6244 for storing and            managing protocol information for one or more protocols            (e.g., standard wireless protocols, such as ZigBee, Z-Wave,            etc., and/or custom or standard wired protocols, such as            Ethernet); and    -   Trigger Detection Module 626 for detecting trigger events (e.g.,        using optional built-in sensors and inputs of the hub device        180, smart devices 204, and/or any other devices in the smart        security network 1100), providing notifications of detected        trigger events, managing and identifying user activity patterns        (e.g., recording user behavior and identifying behavioral        patterns); and    -   Security Protocol Module 628 for executing or declining to        execute security protocols and other operations (e.g.,        coordinating operations of one or more systems and devices of a        smart security network 1100 in accordance with user inputs        corresponding to instructions to execute a security protocol,        the user inputs received through hub device communication module        618 and/or radio communication module 620).

Each of the above identified elements (e.g., modules stored in memory206 of hub device 180) may be stored in one or more of the previouslymentioned memory devices (e.g., the memory of any of the smart devicesin smart home environment 100, FIG. 1), and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory606, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 606, optionally, stores additionalmodules and data structures not described above.

FIG. 7 is a block diagram illustrating the hub server system 508 inaccordance with some implementations. The hub server system 508,typically, includes one or more processing units (CPUs) 702, one or morenetwork interfaces 704 (e.g., including an I/O interface to one or moreclient devices and an I/O interface to one or more electronic devices),memory 706, and one or more communication buses 708 for interconnectingthese components (sometimes called a chipset). Memory 706 includeshigh-speed random access memory, such as DRAM, SRAM, DDR RAM, or otherrandom access solid state memory devices; and, optionally, includesnon-volatile memory, such as one or more magnetic disk storage devices,one or more optical disk storage devices, one or more flash memorydevices, or one or more other non-volatile solid state storage devices.Memory 706, optionally, includes one or more storage devices remotelylocated from one or more processing units 702. Memory 706, oralternatively the non-volatile memory within memory 706, includes anon-transitory computer readable storage medium. In someimplementations, memory 706, or the non-transitory computer readablestorage medium of memory 706, stores the following programs, modules,and data structures, or a subset or superset thereof:

-   -   Operating system 710 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 712 for connecting the hub server        system 508 to other systems, devices, and entities (e.g., client        devices, electronic devices, and systems connected to one or        more networks 162, such as security call center 1102, emergency        responders 1104, smart home provider server system 164, client        devices 504, smart home environments 100, etc.) via one or more        network interfaces 704 (wired or wireless);    -   Server-side module 714, which provides server-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Data receiving module 7140 for receiving data from            electronic devices (e.g., video data from a camera 118,            FIG. 1) via the hub device 180, and preparing the received            data for further processing and storage in the data storage            database 7160;        -   Hub and device control module 7142 for generating and            sending server-initiated control commands to modify            operation modes of electronic devices (e.g., devices of a            smart home environment 100), and/or receiving (e.g., from            client devices 504) and forwarding user-initiated control            commands to modify operation modes of the electronic            devices;        -   Data processing module 7144 for processing the data provided            by the electronic devices, and/or preparing and sending            processed data to a device for review (e.g., client devices            504 for review by a user);        -   Trigger Detection Module 7146 for detecting trigger events            (e.g., based on data from optional built-in sensors and            inputs of the hub device 180, smart devices 204, and/or any            other devices in the smart security network 1100, received            from network communication module 712 and/or data receiving            module 7140), providing notifications of detected trigger            events, managing and identifying user activity patterns            (e.g., recording user behavior and identifying behavioral            patterns); and        -   Security Protocol Module 7148 for executing or declining to            execute security protocols and other operations (e.g.,            coordinating operations of one or more systems and devices            of a smart security network 1100 in accordance with user            inputs corresponding to instructions to execute a security            protocol, the user inputs received from network            communication module 712 and/or data receiving module 7140);            and    -   Server database 716, including but not limited to:        -   Data storage database 7160 for storing data associated with            each electronic device (e.g., each camera) of each user            account, as well as data processing models, processed data            results, and other relevant metadata (e.g., names of data            results, location of electronic device, creation time,            duration, settings of the electronic device, etc.)            associated with the data, wherein (optionally) all or a            portion of the data and/or processing associated with the            hub device 180 or smart devices are stored securely;        -   Account database 7162 for storing account information for            user accounts, including user account information,            information and settings for linked hub devices and            electronic devices (e.g., hub device identifications), hub            device specific secrets, relevant user and hardware            characteristics (e.g., service tier, device model, storage            capacity, processing capabilities, etc.), user interface            settings, data review preferences, etc., where the            information for associated electronic devices includes, but            is not limited to, one or more device identifiers (e.g., MAC            address and UUID), device specific secrets, and displayed            titles; and        -   Device Information Database 7164 for storing device            information related to one or more hub devices, e.g., device            identifiers and hub device specific secrets, independently            of whether the corresponding hub devices have been            associated with any user account.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory706, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 706, optionally, stores additionalmodules and data structures not described above.

FIG. 8 is a block diagram illustrating a representative client device504 associated with a user account in accordance with someimplementations. The client device 504, typically, includes one or moreprocessing units (CPUs) 802, one or more network interfaces 804, memory806, and one or more communication buses 808 for interconnecting thesecomponents (sometimes called a chipset). Optionally, the client devicealso includes a user interface 810 and one or more built-in sensors 890(e.g., accelerometer and gyroscope). User interface 810 includes one ormore output devices 812 that enable presentation of media content,including one or more speakers and/or one or more visual displays. Userinterface 810 also includes one or more input devices 814, includinguser interface components that facilitate user input such as a keyboard,a mouse, a voice-command input unit or microphone, a touch screendisplay, a touch-sensitive input pad, a gesture capturing camera, orother input buttons or controls. Furthermore, some the client devicesuse a microphone and voice recognition or a camera and gesturerecognition to supplement or replace the keyboard. In someimplementations, the client device includes one or more cameras,scanners, or photo sensor units for capturing images (not shown).Optionally, the client device includes a location detection device 816,such as a GPS (global positioning satellite) or other geo-locationreceiver, for determining the location of the client device.

Memory 806 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 806, optionally, includes one or more storagedevices remotely located from one or more processing units 802. Memory806, or alternatively the non-volatile memory within memory 806,includes a non-transitory computer readable storage medium. In someimplementations, memory 806, or the non-transitory computer readablestorage medium of memory 806, stores the following programs, modules,and data structures, or a subset or superset thereof:

-   -   Operating system 818 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 820 for connecting the client        device 504 to other devices, systems, and entities (e.g., client        devices, electronic devices, and systems connected to one or        more networks 162, such as security call center 1102, emergency        responders 1104, smart home provider server system 164, client        devices 504, smart home environments 100, etc.) via one or more        network interfaces 804 (wired or wireless);    -   Input processing module 822 for detecting one or more user        inputs or interactions from one of the one or more input devices        814 and interpreting the detected input or interaction;    -   One or more applications 824 for execution by the client device        (e.g., games, social network applications, smart home        applications, and/or other web or non-web based applications)        for controlling devices (e.g., sending commands, configuring        settings, etc. to hub devices and/or other client or electronic        devices) and for reviewing data captured by the devices (e.g.,        device status and settings, captured data, or other information        regarding the hub device or other connected devices);    -   User interface module 826 for providing and displaying a user        interface in which settings, captured data, and/or other data        for one or more devices (e.g., smart devices 204 in smart home        environment 100) can be configured and/or viewed, for displaying        notifications of trigger events (e.g., the GUI and notification        1300 of FIG. 13A), and/or for detecting user inputs (e.g., user        input indicating selection of a UI element, FIG. 13C);    -   Client-side module 828, which provides client-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Hub device and device control module 8280 for generating            control commands for modifying an operating mode of the hub            device or the electronic devices in accordance with user            inputs; and        -   Data review module 8282 for providing user interfaces for            reviewing data processed by the hub server system 508;    -   Client data 830 storing data associated with the user account        and electronic devices, including, but is not limited to:        -   Account data 8300 storing information related to both user            accounts loaded on the client device and electronic devices            (e.g., of the video sources 522) associated with the user            accounts, wherein such information includes cached login            credentials, hub device identifiers (e.g., MAC addresses and            UUIDs), electronic device identifiers (e.g., MAC addresses            and UUIDs), user interface settings, display preferences,            authentication tokens and tags, password keys, etc.; and        -   Local data storage database 8302 for selectively storing raw            or processed data associated with electronic devices (e.g.,            of the video sources 522, such as a camera 118);    -   Trigger Detection Module 832 for detecting trigger events (e.g.,        using optional built-in sensors and inputs of the hub device        180, smart devices 204, and/or any other devices in the smart        security network 1100), providing notifications of detected        trigger events, managing and identifying user activity patterns        (e.g., recording user behavior and identifying behavioral        patterns); and    -   Security Protocol Module 834 for executing or declining to        execute security protocols and other operations (e.g.,        coordinating operations of one or more systems and devices of a        smart security network 1100 in accordance with user inputs        corresponding to instructions to execute a security protocol).

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, modules or datastructures, and thus various subsets of these modules may be combined orotherwise re-arranged in various implementations. In someimplementations, memory 806, optionally, stores a subset of the modulesand data structures identified above. Furthermore, memory 806,optionally, stores additional modules and data structures not describedabove.

FIG. 9 is a block diagram illustrating a representative smart device 204in accordance with some implementations. In some implementations, thesmart device 204 (e.g., any devices of a smart home environment 100,FIGS. 1 and 2) includes one or more processing units (e.g., CPUs, ASICs,FPGAs, microprocessors, and the like) 902, one or more communicationinterfaces 904, memory 906, radios 940, and one or more communicationbuses 908 for interconnecting these components (sometimes called achipset). In some implementations, user interface 910 includes one ormore output devices 912 that enable presentation of media content,including one or more speakers and/or one or more visual displays. Insome implementations, user interface 910 also includes one or more inputdevices 914, including user interface components that facilitate userinput such as a keyboard, a mouse, a voice-command input unit ormicrophone, a touch screen display, a touch-sensitive input pad, agesture capturing camera, or other input buttons or controls.Furthermore, some smart devices 204 use a microphone and voicerecognition or a camera and gesture recognition to supplement or replacethe keyboard. In some implementations, the smart device 204 includes oneor more image/video capture devices 918 (e.g., cameras, video cameras,scanners, photo sensor units). Optionally, the client device includes alocation detection device 916, such as a GPS (global positioningsatellite) or other geo-location receiver, for determining the locationof the smart device 204.

The built-in sensors 990 include, for example, one or more thermalradiation sensors, ambient temperature sensors, humidity sensors, IRsensors, occupancy sensors (e.g., using RFID sensors), ambient lightsensors, motion detectors, accelerometers, and/or gyroscopes.

The radios 940 enable one or more radio communication networks in thesmart home environments, and allow a smart device 204 to communicatewith other devices. In some implementations, the radios 940 are capableof data communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) custom orstandard wired protocols (e.g., Ethernet, HomePlug, etc.), and/or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Communication interfaces 904 include, for example, hardware capable ofdata communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/orany of a variety of custom or standard wired protocols (e.g., Ethernet,HomePlug, etc.), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Memory 906 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 906, or alternatively the non-volatile memorywithin memory 906, includes a non-transitory computer readable storagemedium. In some implementations, memory 906, or the non-transitorycomputer readable storage medium of memory 906, stores the followingprograms, modules, and data structures, or a subset or superset thereof:

-   -   Operating logic 920 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Device communication module 922 for connecting to and        communicating with other network devices, system, and entites        (e.g., network interface 160, such as a router that provides        Internet connectivity, networked storage devices, network        routing devices, server system 508, security call center 1102,        emergency responders 1104, smart home provider server system        164, client devices 504, smart home environments 100, etc.)        connected to one or more networks 162 via one or more        communication interfaces 904 (wired or wireless);    -   Radio Communication Module 924 for connecting the smart device        204 to other devices (e.g., controller devices, smart devices        204 in smart home environment 100, client devices 504) via one        or more radio communication devices (e.g., radios 940)    -   Input processing module 926 for detecting one or more user        inputs or interactions from the one or more input devices 914        and interpreting the detected inputs or interactions;    -   User interface module 928 for providing and displaying a user        interface in which settings, captured data, and/or other data        for one or more devices (e.g., the smart device 204, and/or        other devices in smart home environment 100) can be configured        and/or viewed, for displaying notifications of trigger events        (e.g., the GUI and notification 1300 of FIG. 13A), and/or for        detecting user inputs (e.g., user input indicating selection of        a UI element, FIG. 13C);    -   One or more applications 930 for execution by the smart device        930 (e.g., games, social network applications, smart home        applications, and/or other web or non-web based applications)        for controlling devices (e.g., executing commands, sending        commands, and/or configuring settings of the smart device 204        and/or other client/electronic devices), and for reviewing data        captured by devices (e.g., device status and settings, captured        data, or other information regarding the smart device 204 and/or        other client/electronic devices);    -   Device-side module 932, which provides device-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Command receiving module 9320 for receiving, forwarding,            and/or executing instructions and control commands (e.g.,            from a client device 504, from a smart home provider server            system 164, from user inputs detected on the user interface            910, etc.) for operating the smart device 204;        -   Data processing module 9322 for processing data captured or            received by one or more inputs (e.g., input devices 914,            image/video capture devices 918, location detection device            916), sensors (e.g., built-in sensors 990), interfaces            (e.g., communication interfaces 904, radios 940), and/or            other components of the smart device 204, and for preparing            and sending processed data to a device for review (e.g.,            client devices 504 for review by a user); and    -   Device data 934 storing data associated with devices (e.g., the        smart device 204), including, but is not limited to:        -   Account data 9340 storing information related to user            accounts loaded on the smart device 204, wherein such            information includes cached login credentials, smart device            identifiers (e.g., MAC addresses and UUIDs), user interface            settings, display preferences, authentication tokens and            tags, password keys, etc.; and        -   Local data storage database 9342 for selectively storing raw            or processed data associated with the smart device 204            (e.g., video surveillance footage captured by a camera 118);    -   Trigger Detection Module 936 for detecting trigger events (e.g.,        using optional built-in sensors and inputs of the hub device        180, smart devices 204, and/or any other devices in the smart        security network 1100), providing notifications of detected        trigger events, managing and identifying user activity patterns        (e.g., recording user behavior and identifying behavioral        patterns); and    -   Security Protocol Module 938 for executing or declining to        execute security protocols and other operations (e.g.,        coordinating operations of one or more systems and devices of a        smart security network 1100 in accordance with user inputs        corresponding to instructions to execute a security protocol,        the user inputs received through device communication module 922        and/or radio communication module 924).

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory906, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 906, optionally, stores additionalmodules and data structures not described above.

FIG. 10 is a block diagram illustrating the smart home provider serversystem 164 in accordance with some implementations. The smart homeprovider server system 164, typically, includes one or more processingunits (CPUs) 1002, one or more network interfaces 1004 (e.g., includingan I/O interface to one or more client devices and an I/O interface toone or more electronic devices), memory 1006, and one or morecommunication buses 1008 for interconnecting these components (sometimescalled a chipset). Memory 1006 includes high-speed random access memory,such as DRAM, SRAM, DDR RAM, or other random access solid state memorydevices; and, optionally, includes non-volatile memory, such as one ormore magnetic disk storage devices, one or more optical disk storagedevices, one or more flash memory devices, or one or more othernon-volatile solid state storage devices. Memory 1006, optionally,includes one or more storage devices remotely located from one or moreprocessing units 1002. Memory 1006, or alternatively the non-volatilememory within memory 1006, includes a non-transitory computer readablestorage medium. In some implementations, memory 1006, or thenon-transitory computer readable storage medium of memory 1006, storesthe following programs, modules, and data structures, or a subset orsuperset thereof:

-   -   Operating system 1010 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 1012 for connecting the smart home        provider server system 164 to other systems, devices, and        entities (e.g., client devices, electronic devices, and systems        connected to one or more networks 162, such as security call        center 1102, emergency responders 1104, smart home provider        server system 164, client devices 504, smart home environments        100, etc.) via one or more network interfaces 1004 (wired or        wireless);    -   Server-side module 1014, which provides server-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Data receiving module 10140 for receiving data from            electronic devices (e.g., video data from a camera 118, FIG.            1), and preparing the received data for further processing            and storage in the data storage database 10160;        -   Device control module 10142 for generating and sending            server-initiated control commands to modify operation modes            of electronic devices (e.g., devices of a smart home            environment 100), and/or receiving (e.g., from client            devices 504) and forwarding user-initiated control commands            to modify operation modes of the electronic devices;        -   Data processing module 10144 for processing the data            provided by the electronic devices, and/or preparing and            sending processed data to a device for review (e.g., client            devices 504 for review by a user);        -   Trigger Detection Module 10146 for detecting trigger events            (e.g., based on data from optional built-in sensors and            inputs of the hub device 180, smart devices 204, and/or any            other devices in the smart security network 1100, received            from network communication module 712 and/or data receiving            module 7140), providing notifications of detected trigger            events, managing and identifying user activity patterns            (e.g., recording user behavior and identifying behavioral            patterns); and        -   Security Protocol Module 10148 for executing or declining to            execute security protocols and other operations (e.g.,            coordinating operations of one or more systems and devices            of a smart security network 1100 in accordance with user            inputs corresponding to instructions to execute a security            protocol, the user inputs received from network            communication module 1012 and/or data receiving module            10140); and    -   Server database 1016, including but not limited to:        -   Data storage database 10160 for storing data associated with            each electronic device (e.g., each camera) of each user            account, as well as data processing models, processed data            results, and other relevant metadata (e.g., names of data            results, location of electronic device, creation time,            duration, settings of the electronic device, etc.)            associated with the data, wherein (optionally) all or a            portion of the data and/or processing associated with the            electronic devices are stored securely; and        -   Account database 10162 for storing account information for            user accounts, including user account information,            information and settings for linked hub devices and            electronic devices (e.g., hub device identifications), hub            device specific secrets, relevant user and hardware            characteristics (e.g., service tier, device model, storage            capacity, processing capabilities, etc.), user interface            settings, data review preferences, etc., where the            information for associated electronic devices includes, but            is not limited to, one or more device identifiers (e.g., MAC            address and UUID), device specific secrets, and displayed            titles.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory1006, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 1006, optionally, storesadditional modules and data structures not described above.

Furthermore, in some implementations, the functions of any of thedevices and systems described herein (e.g., hub device 180, hub serversystem 508, client device 504, smart device 204, smart home providerserver system 164) are interchangeable with one another and may beperformed by any other devices or systems, where the correspondingsub-modules of these functions may additionally and/or alternatively belocated within and executed by any of the devices and systems. As oneexample, referring to FIG. 12, the camera 118-2 may detect the triggerevent (e.g., presence of an unverified user 1202), while the smart alarmsystem 122 provides a notification to the client device 504-1 and thehub device 180 executes a first security protocol. The devices andsystems shown in and described with respect to FIGS. 6-10 are merelyillustrative, and different configurations of the modules forimplementing the functions described herein are possible in variousimplementations.

FIG. 11 is an example smart security network 1100, in accordance withsome implementations. A smart security network 1100 may include anetwork 162 (e.g., Internet) through which multiple entities and devicescommunicate and operate. Such entities and devices may include smarthome environments 100 (e.g., FIGS. 1 and 12) with multiple devices(e.g., smart devices of FIGS. 1 and 2), a security call center 1102, asmart home provider server system 164, emergency responders 1104, andclient devices 504 (e.g., client device 504, FIG. 8).

By establishing interconnectivity and cross-communications betweenentities and devices within a smart security network 1100, usersassociated with a smart home environment 100 may be promptly notifiedand alerted as to any suspicious events concerning their property, suchas the presence of potential intruders on the premises. In particular,the smart security network 1100 enables one or more devices of the smarthome environments 100 (e.g., smart devices of FIGS. 1 and 2) to act as anetwork of diverse and robust sensors that sense various characteristicsof their surrounding environment, which collectively provides users witha comprehensive understanding of a potentially suspicious activity.Given the comprehensive awareness provided by the devices of a smarthome environments 100, users who may not be present at the premises aregiven a more accurate understanding of whether the suspicious event infact requires further notifying others of the smart security network1100 (e.g., alerting emergency responders 1104 and/or a security callcenter 1102), or whether the event is a false alarm (e.g., a relativeexpectedly entering the house). Consequently, users are given granularcontrol in responding to a detected event by executing predefinedsecurity protocols, which may involve controlling devices of the smarthome environments 100 (e.g., presenting an authentication request to anunverified user), or notifying other entities (e.g., security callcenter 1102) to take action.

As described previously with respect to FIGS. 1-4, a smart homeenvironment 100 may include multiple devices (e.g., smart devices, suchas devices 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, and/or 120of FIG. 1, smart devices 204 of FIG. 2, and/or a hub device 180) and anetwork interface (e.g., network interface 160, such as a router) forcommunicating with other entities and devices within the smart securitynetwork 1100. In addition to providing users with a situationalawareness of activities occurring on the premises, devices in the smarthome environment 100 may coordinate with one another to executepredefined security protocols (as described in greater detail withrespect to FIGS. 14A-14E). In some implementations, devices in one smarthome environment 100 may also communicate with devices in a differentsmart home environment 100 (e.g., devices of a first smart homeenvironment 100 send notifications to devices of neighboring smart homeenvironments 100, notifying neighbors that an intruder has beendetected).

Devices of a smart home environment 100 may be controlled by and maysend notifications to client devices 504 associated with authorizedusers of the smart home environment 100 (e.g., client device 504-1receives a notification 1300, and user provides a user input indicatingselection of the UI element 1316 corresponding to instructions soundalarm, FIG. 13A). Furthermore, in some implementations, client devices504 may be used to alert and send notifications to other entities of asmart security network 1100 (e.g., security call center 1102, emergencyresponders 1104), or to communicate with other client devices 504 of thesmart security network (e.g., neighbors, other members of thehousehold).

The smart home provider server system 164 (as described previously) maybe associated with a manufacturer, support entity, or service providerassociated with the devices of a smart home environment 100. In thecontext of a smart security network 1100, the smart home provider serversystem 164 may coordinate one or more operations of smart devices in thesmart home environment 100 (e.g., by sending/executing commands orinstructions to one or more devices in accordance with a predefinedsecurity protocol). In some implementations, the smart home providerserver system 164 also stores data received from the devices of a smarthome environment 100, and may provide that data for use by otherentities or devices within the smart security network 1100 (e.g., thesmart home provider server system 164 stores surveillance footagecaptured by a camera 118-2 of a smart home environment 100 in FIG. 12,and transmits the footage to client devices 504, other smart homeenvironments 100 in the neighborhood, the security call center 1102, andemergency responders 1104).

A security call center 1102 provides security services for one or moresmart home environments 100. The security call center 1102 may includepersonnel (e.g., service representatives) and devices (e.g., serversystems, telephone hotlines) for communicating with other entities ordevices within the smart security network 1100 (e.g., receivingnotifications from and sending commands to devices of a smart homeenvironment 100, communicating with emergency responders 1104).

Emergency responders 1104 include organizations and entities thatprovide security, medical, and hazard related services to a community.Examples include law enforcements agencies (e.g., local police),emergency medical service providers (e.g., hospitals), firefighters,and/or other government or third-party agencies.

As a non-limiting example for describing the interconnectivity ofentities and devices within a smart security network 1100, referring toFIG. 11, an authorized user associated with the smart home environment100-1 may receive a notification on the client device 504-1 regarding apotential intruder on the premises, detected by multiple devices (e.g.,camera 118-2, hub device 180, FIG. 12). The notification may be in theform of a video captured by the camera 118-2, which is stored in, andtransmitted to the user from, the smart home provider server system 164.In response, the authorized user may execute a security protocol,alerting the security call center 1102 who may then contact emergencyresponders 1104 (e.g., police) to investigate the premises. At the sametime, executing the security protocol may also include sendinginstructions to devices of the smart home environment 100-1, such ascommands to the smart alarm system 122 to sound an alarm on thepremises, or commands to actuate a bolt of the smart doorlock 120 totemporarily lock-in the potential intruder. The security protocol mayfurther include alerting neighbors of the user, for example by sendingnotifications to other smart home environments (e.g., 100-2 and 100-3)and client devices (e.g., 504-2 and 504-3).

FIG. 12 is an example smart home environment 100 in a smart securitynetwork 1100, in accordance with some implementations. In the exampleillustrated, the smart home environment 100 consists of a structure 150with multiple rooms 1200, throughout which a variety of devices (e.g.,smart devices) are positioned. Devices include a smart hazard detector104, smart appliances 112 (e.g., washing machine, television), a smartthermostat 102, smart wall switches 108, a smart wall plug 110, a hubdevice 180, cameras 118, a smart doorbell 106, a smart doorlock 120, anda smart alarm system 122. The devices in the smart home environment 100combine to create a mesh network through which data and instructions canbe exchanged between devices, and communication with other entities,users, and devices of the smart security network 1100 is enabled (e.g.,through a network interface 160). The smart home environment 100 (or anycombination of devices within the smart home environment 100) issometimes referred to as a “security system.” Other implementations ofthe smart home environment 100 may include additional devices, systems,or entities not shown in FIG. 12 (e.g., security call center 1102, smarthome provider server system 164, emergency responders 1104), which havemerely been omitted for the sake of brevity and so as to not obscure thepertinent aspects of the implementation.

Smart home environments 100 and associated devices are described ingreater detail with respect to FIG. 1. Thus, while some features of thesmart home environment 100 in FIG. 12 are discussed, other features havenot been so as not to obscure more pertinent aspects of the exampleimplementation disclosed herein. Furthermore, while some example devicesof the smart home environment 100 are illustrated, other implementationsof the smart home environment 100 may include fewer or other additionaldevices.

FIG. 12 illustrates an example in which a trigger event is detected onthe premises of the smart home environment 100. Trigger events areoccurrences detected by one or more devices (e.g., devices in a smarthome environment 100, FIGS. 1 and 12) that may or may not constitute asecurity breach. Premises upon which a trigger event may be detectedinclude a perimeter established by the smart home environment 100 (e.g.,in a room 1200, on the front yard outside of the structure 150, etc.),or by multiple smart home environments 100 (e.g., within a geo-fenceperimeter established by multiple smart devices across multiple smarthome environments 100 within a neighborhood). Trigger events may includedetection of motion (e.g., a person walking through room 1200-3),openings of entryways (e.g., window, front door, garage), unexpectedactivation/deactivation of devices (e.g., unexpected powering on of thetelevision 112-2), or detection of unusual activity patterns (e.g.,unexpected detection of an individual in the smart home environment 100on a particular day). In some implementations, trigger events aredetected by one or more sensing capabilities of a device (or a group ofdevices) in the smart home environment 100 (e.g., occupancy datagathered by hub device 180 is considered together with surveillancefootage captured by camera 118-2 to confirm presence of an intruder).Various trigger events are described in greater detail with respect toFIGS. 14A-14E.

In this example, an unverified user 1202 is detected in the room 1200-3of the smart home environment 100 by the opening of the front door(e.g., detected by the smart doorbell 106 and/or the smart doorlock120), and by the presence detection capabilities of the devices in theroom (e.g., occupancy sensors of the camera 118-2, hub device 180,and/or the smart alarm system 122). Upon detecting the trigger event,one or more devices of the smart home environment 100 provide anotification to an authorized user who is not currently on the premisesvia a client device 504-1. As described in greater detail below, inresponse to the notification, the authorized user may determine that theunverified user is an intruder, and may then decide to execute apredefined security protocol (e.g., sounding an alarm, alerting thesecurity call center 1102, etc.).

FIGS. 13A-13D illustrate examples of graphical user interfaces (“GUIs”)for displaying notifications and executing operations responsive tonotifications, in accordance with some implementations. The GUIs inthese figures are used to illustrate interfaces related to the processesdescribed below, including the method 1400 (FIGS. 14A-14E). While FIGS.13A-13D illustrate examples of GUIs, in other implementations, one ormore GUIs display user-interface elements in arrangements distinct fromthe implementations of FIGS. 13A-13D.

The GUIs shown in FIGS. 13A-13D may be displayed on any device of asmart security network 1100 having an output component (e.g., display,speaker, tactile feedback generator, etc.), such as mobile phones (e.g.,client devices 504), smart devices (e.g., hub device 180, smarttelevision 112-2, FIG. 1), or other electronic devices (e.g., personalcomputers, tablet computers, etc.). The GUIs may be provided by anapplication for managing devices of a smart home environment 100 (e.g.,applications 824, FIG. 8), and/or a web browser application.

FIG. 13A illustrates a GUI for displaying a notification 1300 andselecting security protocols or operations to be executed. As shown, thenotification 1300 indicates that a trigger event has been detected at asmart home environment 100 (e.g., associated with the authorized user ofthe client device 504). In this example, the notification 1300 indicatesthe particular room (e.g., room 1200-3) in which, and the time (e.g.,1:00 AM) at which the activity was detected.

The GUI of FIG. 13A also displays various user-interface (“UT”) elements(e.g., 1310 to 1322) corresponding to security protocols and operationsthat an authorized user may choose to execute or decline to execute.Security protocols include one or a series of operations to be performedby one or more devices in a smart security network 1100. For example,executing a security protocol may include presenting a security questionto the unverified user 1202 (e.g., by outputting audio through abuilt-in speaker in the hub device 180), monitoring for a response(e.g., using a built-in microphone of the camera 118-2), and soundingthe alarm (e.g., in the smart alarm system 122) if the unverified useris determined to be an intruder.

In some implementations, in response to the notification 1300, a userinput is detected (e.g., tap selection on a touch-sensitive display ofthe client device 504). Depending on the UT element selected, the userinput corresponds to instructions to either execute or decline executionof a security protocol or operation. For example, in FIG. 13A, theauthorized user may choose to: (1) view a live video feed (e.g., UIelement 1310, causing surveillance footage captured by the camera 118-2to be streamed to the client device 504-1, FIG. 12), (2) ignore thetrigger event (e.g., UI element 1312, disarming smart alarm system 122and declining to sound the alarm), (3) defer action (e.g., UI element1314, sending the notification 1300 to a device of another householdmember to determine what action is to be taken), (4) sound the alarm(e.g., UI element 1316, causing the smart alarm system 122 to sound thealarm), (5) present a security question (e.g., UI element 1318, causingaudio to be output through a built-in speaker of the camera 118-2), (6)alert a security call center (e.g., UI element 1320, causing anotification to be sent to the security call center 1102, FIG. 11),and/or (7) alert the police (e.g., UI element 1322, causing anotification to be sent to emergency responders 1104, FIG. 11). The GUIof FIG. 13A may also include an optional UI element which, whenselected, executes a security protocol allowing the user to view apreviously-recorded, rather than live video stream (e.g., UI element1311, “View Clip/Photo”). This would be advantageous in situations inwhich a user or homeowner is slow to receive the notification 1300 andan unverified user has moved out of the video frame.

FIG. 13B illustrates a GUI displayed if the authorized user chooses topresent a security question (e.g., UI element 1318, FIG. 13A). As shown,the authorized user may select from several questions (e.g., 1318-1 to1318-4) to present to the unverified user. Alternatively, the authorizeduser may connect directly to a device within proximity to the unverifieduser (e.g., camera 118-2) and directly stream live audio via the clientdevice 504 to be output through the nearby device.

In response to presenting the security question (e.g., selecting UIelement 1318-1, “What is my dog's name?”), the GUI of FIG. 13C isdisplayed. Here, the unverified user has provided a response to thesecurity question (e.g., by speaking into a microphone of the camera118-2, generating an audio file which is then processed using speechrecognition techniques), which is displayed in addition to a request forfurther instructions from the authorized user (e.g., user provides“Pepper” as an answer to the question, 1340). As shown, some optionsthat were available when the authorized user received the initialnotification (FIG. 13A) are also selectable in FIG. 13C. For example,after examining the unverified user's response, the authorized user maynow choose to sound the alarm (e.g., UI element 1316) or alert thesecurity call center 1102 (e.g., UI element 1320). In response toreceiving the unverified user's response to the security question, theauthorized user may additionally choose to listen to the recorded audioof the unverified user (e.g., UI element 1350) to eliminate the risk ofa potential intruder knowing the correct answer, for example. Theauthorized user may also present another security question (e.g., UIelement 1352) to further verify the identity of the unverified user.

Alternatively, if the authorized user chooses to defer action (e.g., UIelement 1314, FIG. 13C), the GUI of FIG. 13D is displayed. Here, theauthorized user may choose to defer action to one or more individuals(e.g., UI elements 1314-1 to 1314-3), such as the user's neighbor,brother, or wife. Consequently, the selected individual may receive (onan associated client device) the notification 1300 as shown in FIG. 13A,and may be given similar options with respect to responding to thenotification.

FIGS. 13A-13D illustrate only examples of GUIs that may be displayed inperforming the method 1400 described below (FIGS. 14A-14E). It is noted,however, that additional and/or alternative GUIs may be displayed,including UI elements corresponding to alternative and/or additionalsecurity protocols or operations that may be executed.

FIGS. 14A-14E are flow diagrams illustrating a method of detectingtrigger events and executing security protocols, in accordance with someimplementations. In some implementations, the method 1400 is performedby one or more electronic devices of one or more systems (e.g., devicesof a smart home environment 100, FIGS. 1 and 12; devices 204 and/or hubdevice 180 of smart home network 202, FIG. 2), a server system (e.g.,smart home provider server system 164 of FIGS. 1 and 2, hub serversystem 508 of FIG. 5), and/or one or more devices of a security provider(e.g., devices of security call center 102 in FIG. 11, not shown) and/oremergency response provider (e.g., devices of emergency responders 104in FIG. 11, not shown). Thus, in some implementations, the operations ofthe method 1400 described herein are entirely interchangeable, andrespective operations of the method 1400 are performed by any of theaforementioned devices, systems, or combination of devices and/orsystems. For ease of reference, the methods herein will be described asbeing performed by a computer system (e.g., one or more smart devices204 of a smart home environment 100, FIGS. 1, 2, and 9). FIGS. 14A-14Ecorrespond to instructions stored in a computer memory or othercomputer-readable storage medium (e.g., respective memories 906 of oneor more smart devices 204, FIG. 9).

The computer system detects (1402) a trigger event, including detectingan unverified user within the premises. In some implementations,detecting (1402) the trigger event includes detecting (1404) the openingof a door. In some implementations, detecting (1402) the trigger eventincludes receiving (1406) inputs from one or more distinct devices ofthe computer system (e.g., in FIG. 12, audio or video captured by acamera 118-2, motion data captured by a hub device 180, etc.). In someimplementations, inputs may include unique digital fingerprints of arespective device of an unverified user (e.g., GSM Fingerprints). FIG.12 illustrates an example in which multiple devices (e.g., hub device180, camera 118-2, and/or smart alarm system 122) detect the presence ofan unverified user 1202 in a room 1200-3 of the smart home environment100.

In some implementations, detecting (1402) the trigger event includesobtaining (1408) an activity pattern of an authorized user, of one ormore authorized users. Activity patterns indicate behavioralcharacteristics and patterns of users with respect to their actions at apremises over a period of time. For example, in some implementations,the activity pattern for the authorized user (1410) indicates, for arespective day of the week and/or a respective range of time: a timespent in an area (e.g., 5 hours spent in a particular room on Mondays)of the premises, and/or the number of instances in which the authorizeduser entered the area of the premises (e.g., user enters and leaves theroom approximately 5 times in a given day). An activity pattern may alsoindicate a user's device usage patterns, including which devices areused most by a user, with what frequency/duration particular devices areused (e.g., television turned on 3 times a day, television turned on for60 minutes total per day), and/or the settings with which particulardevices are used (e.g., specific radio stations, channels, volume,etc.). Time measurements of an activity pattern spent may be an averageor aggregate amount of time. Furthermore, time measurements may also bea particular hour, range of hours (e.g., between 3:00 PM to 5:00 PM), orgeneral time of day (e.g., morning). In some implementations, theactivity pattern is determined (1412) over a predefined period of time(e.g., over one month). In some implementations, the one or moreauthorized users are authorized occupants of the premises. Authorizedoccupants may include home owners, tenants, or any other type ofindividual expected to be present on or have access to the premises. Insome implementations, machine learning techniques known to those skilledin the art are applied to generate and update user activity patterns.

In these implementations, detecting (1402) the trigger event furtherincludes identifying (1414) an activity pattern of the unverified user,and determining (1416) that the activity pattern of the unverified useris at least partially distinct from the activity pattern of theauthorized user. A trigger event is therefore detected by comparing andidentifying differences between the recorded behavioral patterns of anauthorized user and an unverified user. In some implementations, theactivity patterns of the unverified user and the authorized user aredistinct if the difference with respect to a particular measurementexceeds a threshold value (e.g., total time spent in an particular roomdeviates from a time spent by the authorized user, as indicated theactivity pattern, by more than 1 hour). In some implementations,identifying the activity pattern of an unverified user beginsimmediately upon and continues while detecting the presence of theunverified user on the premises.

In some implementations, a current date and time is determined (1416),and determining (1418) that the activity pattern of the unverified useris at least partially distinct from the activity pattern of theauthorized user is with respect to the current date and time (1420). Inone example, the activity pattern for an authorized user may indicatethat the authorized user only resides on the premises on Mondays betweenthe hours of 9:00 AM and 3:00 PM. Therefore, if the activity pattern ofan unverified user indicates the presence of the unverified user on thepremises at 5:00 PM on Monday, a trigger event is detected.

In some implementations, the user may adjust the sensitivity with whichthe trigger event is detected. Adjusting the sensitivity of the triggerevent may include excluding from trigger event detection particularregions of the premises (e.g., do not consider detected movements in thekitchen) and/or specific ranges/durations of time (e.g., do not considerdetected activity between the times of 9:00 PM and 11:00 PM; do notconsider movement in the kitchen for 5 hours).

Referring now to FIG. 14B, after detecting (1402) the trigger event, anotification regarding the detected trigger event is provided (1422) toone or more authorized users distinct from the unverified user. Forexample, referring to FIG. 11, upon detecting a trigger event in a smarthome environment 100-1, a notification may be provided to an authorizeduser of the smart home environment 100-1, in addition to users of smarthome environments 100-2 and 100-3 who are neighbors of the authorizeduser. In some implementations, the notification includes (1424)information identifying the trigger event. FIG. 13A illustrates anexample, where the notification 1300 states that activity has beendetected in Room 1200-3 at 1:00 AM. In some implementations, providing(1422) the notification also includes streaming video content from acamera that has captured the trigger event (e.g., streaming video fromthe camera 118-2 to the client device 504-1, FIG. 12). In someimplementations, providing (1422) the notification is in accordance withdetecting (1426) that the one or more authorized users are not withinthe premises (e.g., users are outside a predefined perimeter of thepremises or smart home environment). Additionally and/or alternatively,the notification is provided even if one or more authorized users aredetected within the premises.

Responsive to the provided notification, user inputs are received whichcorrespond to instructions to execute one or more security protocolsand/or operations. Security protocols may be represented as selectableoptions on a GUI of a device, where the device is associated with anauthorized user or smart home environment (e.g., UI elements 1310 to1322 corresponding to various security protocols and operations aredisplayed on a client device 504, FIG. 13A). In some implementations, auser input may be a selection detected on a device associated with theauthorized user or smart home environment (e.g., tap-selection and/orvoice command received on a client device 504-1, FIG. 12). In someimplementations, a respective security protocol is associated with arespective authorized user. For example, a security profile of arespective user may include a different set of security questionspredefined by the respective user (e.g., security questions displayed inFIG. 13B correspond to the authorized user associated with the clientdevice 504).

Referring to FIG. 14C, in some implementations, a user input responsiveto the notification and corresponding to instructions to execute a firstsecurity protocol is received (1428) from an authorized user of the oneor more authorized users. In response to receiving (1428) the userinput, the first security protocol is executed (1430). The firstsecurity protocol (1430) includes presenting (1432) to the unverifieduser an authentication request. An authentication request may be asolicitation for a response from the unverified user to verify his orher identity. The authentication request may be presented through anoutput of a device (e.g., speaker and/or display of any devices in thesmart home environment 100, FIG. 12).

In some implementations, the authentication request (1432) includes asecurity question (1434), and the response comprises an answerresponsive to the question. FIGS. 13A and 13B illustrate an example inwhich an authorized user (associated with the client device 504) selectsUI element 1318 (“Present Security Question”) to execute a firstsecurity protocol to present a security question to the unverified user1202 (FIG. 12). In some implementations, the instructions include aselection of the security question, of a plurality of securityquestions, by the authorized user (e.g., selecting one of the UIelements 1318-1 through 1318-4 corresponding to different securityquestions, FIG. 13B). In some implementations, presenting (1432) theauthentication request includes playing (1438) a pre-recorded audio file(e.g., security question pre-recorded by an authorized user). In someimplementations, presenting the authentication request includesreceiving a live audio recording from the respective authorized user,and streaming the received audio to the unverified user (i.e., selectingUI element 1318-5 in FIG. 13B allows an authorized user to speakdirectly to the unverified user).

The premises are monitored (1440) for a response to the authenticationrequest. A response to the authentication request may include an inputprovided to a device (e.g., using an input method of a device in closeproximity to an unverified user, such as a microphone or touch-screendisplay). In some implementations, the response to the authenticationrequest is a recorded audio file (1442). In some implementations, theresponse is a personal identification number (1444). Additionally and/oralternatively, responses to the authentication request may include auser input received on an interactive touch-screen device (e.g.,selection of a response on the touch-screen of the hub device 180), abiometric sample (e.g., fingerprint, retinal scan), a username andpassword, detection of an authenticated RFID device (e.g., RFID tag),wireless pairing of an authenticated device (e.g., Wi-Fi, IR,Bluetooth), and/or any other personal identification means known tothose skilled in the art. In some implementations, presenting theauthentication request includes presenting multiple authenticationrequests (e.g., requiring both fingerprint and voice authenticationsamples).

Based on the response to the authentication request, the unverified useris then determined (1446) to be either an authorized user orunauthorized user. In some implementations, the unverified user isdetermined to be an unauthorized user (and a second security protocolmay consequently be executed) if the response is an incorrect answer toa presented security question. In some implementations, audio processingtechniques (e.g., voice recognition, speech-to-text) are applied (1448)to process the recorded audio file. The recorded audio file maytherefore be automatically compared against voice samples of authorizedusers to determine whether the unverified user is an authorized user.Additionally and/or alternatively, the response to the authenticationrequest is presented (1450) to the authorized user, and a user inputresponsive to the presented response is received (1452) from the firstauthorized user, the user input indicating whether the unverified useris authorized. For example, as shown in FIG. 13C, the user may listen tothe recorded audio of an unverified user (e.g., by selecting UI element1350) and may subsequently sound the alarm (e.g., by selecting UIelement 1316) if he does not recognize the unverified user. Bypresenting the response, the authorized user is therefore better able toprevent unauthorized users who may happen to know a correct answer frombypassing the security protocol.

Referring now to FIG. 14D, based on the response to the authenticationrequest, a second security protocol is executed or declined execution(1454). Compared to the first security protocol, the second securityprotocol may include escalated actions to be performed. Executing thesecond security protocol may, for example, include alerting providers ofemergency response services (e.g., in FIG. 13C, selecting the UI element1320 to alert a security call center 1102 or UI element 1322 to alertemergency responders 1104). In some implementations, executing thesecond security protocol includes sounding (1456) an alarm device (e.g.,sounding smart alarm system 122, FIG. 12).

In some implementations, executing the second security protocol includesproviding (1458) a notification to one or more other authorized users(e.g., sending the notification to other authorized member of thehousehold associated with the smart home environment 100-1, in additionto users of smart home environments 100-2 and 100-3 who are neighbors ofthe authorized user, FIG. 11). In such implementations, the notificationprovided may be a notification of the trigger event, while in otherimplementations, the authorized users who receive the notification mayalso provide user inputs responsive to the notification andcorresponding to instructions to execute a security protocol (e.g.,presented with the GUI of FIG. 13A). Discretion in responding to thedetected trigger event is therefore deferred to other authorized userswho may be better positioned to determine whether the trigger event is afalse alarm, or warrants an escalated action (e.g., a neighbor who has aview of the detected trigger event).

In some implementations, executing the second security protocol includessending (1460) instructions to other devices (e.g., sending instructionsto the smart doorlock 120 to lock an intruder in the house, FIG. 12).

In some implementations, if the unverified user is not an authorizeduser (determined automatically, or manually by an authorized user, step1446 of FIG. 14C), the second security protocol is executed (1462), andif the unverified user is an authorized user, execution of the secondsecurity protocol is declined.

In some implementations, declining execution of the second securityprotocol includes foregoing any subsequent action (e.g., selecting theUI element 1312 to ignore the trigger event, FIG. 13C).

Alternatively, referring now to FIG. 14E, a user input responsive to thenotification and corresponding to instructions to execute the secondsecurity protocol is received (1464) from an authorized user. Inresponse to receiving the user input, the second security protocol isexecuted (1466). Escalated options that are selectable during executionof a first security protocol may therefore also be selectable as analternative to the first security protocol. For example, referring toFIG. 13A-13C, the authorized user may alert the security call centereither after viewing an unverified user's response to a presentedsecurity question (e.g., selecting UI element 1320, FIG. 13C), oralternatively may do so immediately in response to receiving thenotification of the trigger event, without first presenting the securityquestion (e.g., selecting UI element 1320, FIG. 13A).

In some implementations, a user input responsive to the notification andcorresponding to instructions to execute a third security protocol isreceived from an authorized user. In response to receiving the userinput, the third security protocol is executed, wherein the firstsecurity protocol, the second security protocol, and the third securityprotocol are distinct. Upon receiving the notification, the user maytherefore choose a desired escalation path (e.g., first securityprotocol presents a security question, second security protocol includesalerting a call center, and third security protocol defers action to aneighbor).

In some implementations, a user input corresponding to instructions toaccess other devices, distinct from one or more devices of the computersystem, is received (1468). Data is retrieved (1470) from the otherdevices, and the data is provided (1472) to the one or more authorizedusers. For example, once the authorized user is notified of the triggerevent (e.g., detected by smart alarm system 122, FIG. 12), the user mayaccess additional devices to determine whether the unverified user is anauthorized user (e.g., accessing surveillance footage captured by acamera 118-2, FIG. 12).

In some implementations, in the absence of receiving a user inputresponsive to the notification, the first security protocol is executed(1474). For example, a user input may not be received if the authorizeduser lacks network connectivity (e.g., no cellular or Internetconnection to the network 162, FIG. 12), or if the electronic deviceproviding the notification of the trigger event or receiving the userinput does not have network connectivity (e.g., due to power outage,device malfunction, etc.). Alternatively, in the absence of receiving auser input responsive to the notification, the second security protocolis executed (e.g., immediate escalation).

In some implementations, in the absence of receiving from the unverifieduser the response to the authentication request, the second securityprotocol is executed. In some implementations, the second securityprotocol is executed if the response is not received by a predefinedtime limit (e.g., within 30 seconds).

In some implementations, in response to detecting the trigger event (at1402, FIG. 14A), the first security protocol is automatically (i.e.,without a user input) executed. For example, in response to detectingthe presence of an unverified user, a security question willautomatically be presented, and a subsequent operation will be executedbased on the unverified user's response.

In some implementations, prior to detecting a trigger event, a userinput is received from an authorized user who is not within thepremises, the user input corresponding to instructions to execute asecurity protocol. When executed, the security protocol includespresenting an authentication request and monitoring the premises for aresponse to the authentication request. If no response to theauthentication request is detected, an arming protocol is executed(e.g., arming the smart alarm system 122, FIG. 12). Alternatively, if aresponse to the authentication request is detected, no action isperformed. In some implementations, no action is performed if theauthentication request is a security question, and the response to theauthentication request is a correct answer to the security question. Insome implementations, subsequent to executing the arming protocol, thetrigger event is detected, where a security protocol (distinct from thesecurity protocol for presenting the authentication request) is executedin response to detecting the trigger event (e.g., sounding an alarm,contacting security call center, etc.). Consequently, an authorized userwho has left the premises unarmed can preemptively utilize anauthentication request to determine whether other authorized occupantsof the premises are present. If so, based on responses received to theauthentication request, the premises will remain unarmed. However, if noresponses are received, the premises will be armed, and any subsequentlydetected trigger events will automatically execute a predefined securityprotocol (e.g., sounding an alarm).

In some implementations, detecting the trigger event based on anactivity pattern of the unverified user (1408) is further based onreceived user inputs for executing or declining to execute a securityprotocol (e.g., step 1454, 1466, etc.). As an example, detecting atrigger event may include detecting that a housekeeper who does not havean authorized client device has entered the premises through a side doorof the premises every Monday at 9:00 AM. An authorized user, uponreceiving a notification, may provide a user input for declining toexecute a security protocol (e.g., declining to sound the alarm).Consequently, the activity pattern of the unverified user is modifiedsuch that similar activities detected in the future (e.g., side doorentry every Monday at 9:00 AM) will not constitute the detection of atrigger event. In some implementations, modifying the activity patternof the unverified user based on received user inputs is in accordancewith the number of received user inputs in response to the detectedactivity pattern of the unverified user satisfying a threshold (e.g.,declining to execute security protocol more than 5 times). User inputstherefore provide a feedback mechanism by which the computer system“learns” and better determines whether potentially suspicious activityis actually a trigger event that warrants further action. In someimplementations, machine learning techniques are utilized to train theactivity pattern of unverified users.

In some implementations, security protocols may combine any of theoperations or features of the security protocols discussed herein (e.g.,executing a predefined security protocol sounds an alarm and alsonotifies security call center). These security protocols may includeperforming one or more operations in a predefined sequence or order(e.g., notifying neighbors first before sounding the alarm). Asindicated previously, the terms first, second, etc. used herein todescribe various elements that are not to be limited by these terms, andare only used to distinguish one element from another. Thus, steps ofthe method 1400 (FIGS. 14A-14E) are not limited by the respectivesecurity protocols and/or user inputs with respect to which they aredescribed (e.g., in step 1474 of FIG. 14E, in the absence of receiving auser input responsive to the notification, any security protocol (first,second, third, etc.) described herein may be executed).

For situations in which the systems discussed above collect informationabout users, the users may be provided with an opportunity to opt in/outof programs or features that may collect personal information (e.g.,information about a user's preferences or usage of a smart device). Inaddition, in some implementations, certain data may be anonymized in oneor more ways before it is stored or used, so that personallyidentifiable information is removed. For example, a user's identity maybe anonymized so that the personally identifiable information cannot bedetermined for or associated with the user, and so that user preferencesor user interactions are generalized (for example, generalized based onuser demographics) rather than associated with a particular user.

Although some of various drawings illustrate a number of logical stagesin a particular order, stages that are not order dependent may bereordered and other stages may be combined or broken out. While somereordering or other groupings are specifically mentioned, others will beobvious to those of ordinary skill in the art, so the ordering andgroupings presented herein are not an exhaustive list of alternatives.Moreover, it should be recognized that the stages could be implementedin hardware, firmware, software or any combination thereof.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific implementations. However, theillustrative discussions above are not intended to be exhaustive or tolimit the scope of the claims to the precise forms disclosed. Manymodifications and variations are possible in view of the aboveteachings. The implementations were chosen in order to best explain theprinciples underlying the claims and their practical applications, tothereby enable others skilled in the art to best use the implementationswith various modifications as are suited to the particular usescontemplated.

1. (canceled)
 2. A method, comprising: at a server system having one ormore processors and memory storing instructions for execution by the oneor more processors, wherein the server system is coupled to a securitydevice system and a client device via one or more wide area networks,and the security device system is located at a premises, and wherein theserver system is located remotely from the premises: in response todetection of a trigger event associated with the security device system,providing a notification regarding the trigger event associated with thesecurity device system to one or more authorized users via the wide areanetworks for display on a user interface of an application executed onthe client device; causing the application to present on the userinterface a plurality of security protocol/operation options that isselectable by a first authorized user for execution by the securitydevice system, the plurality of security protocol/operation optionsincluding a first security protocol/operation option of presenting apredefined system-generated audible security message via the securitydevice system; receiving, from the first authorized user of the one ormore authorized users, a first user input selecting the first securityprotocol/operation option in response to the notification; and inresponse to receiving the first user input, executing the first securityprotocol/operation option at the premises, including: causing theapplication to present on the user interface a plurality of securitymessages corresponding to a plurality of predefined system-generatedaudible security messages, and receiving from the first authorized usera second user input selecting one of the plurality of security messagesfor presenting a corresponding predefined system-generated audiblesecurity message via the security device system.
 3. The method of claim2, wherein the plurality of security messages includes a securityquestion corresponding to a predefined system-generated audible securityquestion, further comprising: receiving over the wide area networks aresponse to the predefined system-generated audible security question,the response being collected by the security device system in thepremises.
 4. The method of claim 2, wherein the security device systemfurther comprises one or more of: a surveillance device configured tocollect data used for detecting the trigger event associated with thesecurity device system within the premises; a speaker configured topresent to a person the predefined system-generated audible securitymessage corresponding to the selected one of the plurality of securitymessages; and a microphone configured to collect a response to thepredefined system-generated audible security message corresponding tothe selected one of the plurality of security messages at the premises.5. The method of claim 2, wherein the trigger event associated with thesecurity device system includes detection of a person, providing thenotification further comprises providing a time of detection of theperson and a corresponding location of the detected person, thecorresponding location being within the premises.
 6. The method of claim5, wherein the person is detected according to a predeterminedsensitivity that excludes a region of the premises from detection orspecifies a range of time for detection.
 7. The method of claim 2,wherein the trigger event associated with the security device systemincludes an activation of the security device system.
 8. The method ofclaim 2, further comprising: after receiving a response to the selectedone of the plurality of security messages: receiving, by the serversystem and over the wide area networks, a third user input that selectsa first security protocol from a plurality of additional securityoptions; and in accordance with the selected first security protocol,sounding an alarm device.
 9. The method of claim 2, further comprising:after receiving a response to the selected one of the plurality ofsecurity messages: receiving, by the server system and over the widearea networks, a third user input that selects a first security protocolfrom a plurality of additional security options; and in accordance withthe selected first security protocol, providing a notification to thepolice or one or more other authorized users associated with clientdevices that are distinct from the security device system.
 10. Themethod of claim 2, further comprising: causing the application topresent on the user interface a plurality of additional securityprotocol/operation options including at least alerting the police. 11.The method of claim 2, further comprising: causing the application topresent on the user interface a plurality of additional securityprotocol/operation options including at least communicating with one ormore other client devices.
 12. The method of claim 2, wherein thesecurity device system includes a network-connected doorbell device. 13.The method of claim 2, wherein the plurality of security messages ispresented on the user interface of the application in place of the firstsecurity protocol/operation option.
 14. A non-transitory computerreadable storage medium, storing one or more programs for execution byone or more processors of a server system, wherein the server system iscoupled to a security device system and a client device via one or morewide area networks, and the security device system is located at apremises, and wherein the server system is located remotely from thepremises, the one or more programs including instructions for: inresponse to detection of a trigger event associated with the securitydevice system, providing a notification regarding the trigger eventassociated with the security device system to one or more authorizedusers via the wide area networks for display on a user interface of anapplication executed on the client device; causing the application topresent on the user interface a plurality of security protocol/operationoptions that is selectable by a first authorized user for execution bythe security device system, the plurality of security protocol/operationoptions including a first security protocol/operation option ofpresenting a predefined system-generated audible security message viathe security device system; receiving, from the first authorized user ofthe one or more authorized users, a first user input selecting the firstsecurity protocol/operation option in response to the notification; andin response to receiving the first user input, executing the firstsecurity protocol/operation option at the premises, including: causingthe application to present on the user interface a plurality of securitymessages corresponding to a plurality of predefined system-generatedaudible security messages, and receiving from the first authorized usera second user input selecting one of the plurality of security messagesfor presenting a corresponding predefined system-generated audiblesecurity message via the security device system.
 15. The non-transitorycomputer readable storage medium of claim 14, wherein the trigger eventassociated with the security device system includes detection of aperson, providing the notification further comprises providing a time ofdetection of the person and a corresponding location of the detectedperson, the corresponding location being within the premises.
 16. Thenon-transitory computer readable storage medium of claim 15, wherein theperson is detected according to a predetermined sensitivity thatexcludes a region of the premises from detection or specifies a range oftime for detection.
 17. The non-transitory computer readable storagemedium of claim 14, wherein the trigger event associated with thesecurity device system includes an activation of the security devicesystem.
 18. A method, comprising: at a client device having one or moreprocessors and memory storing instructions for execution by the one ormore processors, wherein the client device is coupled to a securitydevice system and a server system via one or more wide area networks,and the security device system is located at a premises, and wherein theserver system is located remotely from the premises: in response todetection of a trigger event associated with the security device system,providing a notification regarding the trigger event associated with thesecurity device system to one or more authorized users via the wide areanetworks for display on a user interface of an application executed onthe client device; presenting on the user interface of the application aplurality of security protocol/operation options that is selectable by afirst authorized user for execution by the security device system, theplurality of security protocol/operation options including a firstsecurity protocol/operation option of presenting a predefinedsystem-generated audible security message via the security devicesystem; receiving, from the first authorized user of the one or moreauthorized users, a first user input selecting the first securityprotocol/operation option in response to the notification; and inresponse to receiving the first user input, enabling execution of thefirst security protocol/operation option at the premises, including:presenting on the user interface of the application a plurality ofsecurity messages corresponding to a plurality of predefinedsystem-generated audible security messages, and receiving from the firstauthorized user a second user input selecting one of the plurality ofsecurity messages for presenting a corresponding predefinedsystem-generated audible security message via the security devicesystem.
 19. The method of claim 18, wherein providing the notificationfurther comprises configuring the notification for display on the userinterface of the application executed on the client device, and thefirst user input is entered on the user interface of the applicationexecuted on the client device and corresponds to instructions to executethe first security protocol/operation option.
 20. The method of claim18, further comprising: presenting on the user interface of theapplication a plurality of additional security protocol/operationoptions including at least alerting the police.
 21. The method of claim18, further comprising: presenting on the user interface of theapplication a plurality of additional security protocol/operationoptions including at least communicating with one or more other clientdevices.